X2Go Bug report logs - #1458
unattended Debian installations (using preseed) fail when x2gobroker-ssh is involved

version graph

Package: x2gobroker-ssh; Maintainer for x2gobroker-ssh is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2gobroker-ssh is src:x2gobroker.

Reported by: Stefan Baur <X2Go-ML-1@baur-itcs.de>

Date: Fri, 17 Apr 2020 14:10:54 UTC

Severity: normal

Tags: pending

Fixed in version 0.0.4.2

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1458: [X2Go-Dev] Bug#1458: Bug#1458: unattended Debian installations (using preseed) fail when x2gobroker-ssh is involved
Reply-To: Ulrich Sibiller <uli42@gmx.de>, 1458@bugs.x2go.org
Resent-From: Ulrich Sibiller <uli42@gmx.de>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 17 Apr 2020 18:05:33 +0000
Resent-Message-ID: <handler.1458.B1458.158714666414865@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1458
X-X2Go-PR-Package: x2gobroker-ssh
X-X2Go-PR-Keywords: 
References: <09a01d9f-1db4-ad20-e0f5-d08889ab89f6@baur-itcs.de> <CANVnVYJuGhHgK0o2RNZ15-V80faqGY1ngcWaH+6oM4LJGW-5mg@mail.gmail.com> <ae83255d-c9ca-fab9-d0f1-cd3325e720f2@baur-itcs.de> <09a01d9f-1db4-ad20-e0f5-d08889ab89f6@baur-itcs.de>
Received: via spool by 1458-submit@bugs.x2go.org id=B1458.158714666414865
          (code B ref 1458); Fri, 17 Apr 2020 18:05:33 +0000
Received: (at 1458) by bugs.x2go.org; 17 Apr 2020 18:04:24 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=3.0 tests=BAYES_20,FREEMAIL_FROM,
	RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,URIBL_BLOCKED autolearn=ham
	autolearn_force=no version=3.4.2
Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id BE3465DAE5
	for <1458@bugs.x2go.org>; Fri, 17 Apr 2020 20:02:59 +0200 (CEST)
Received: by mail-yb1-f176.google.com with SMTP id b17so1313520ybq.13
        for <1458@bugs.x2go.org>; Fri, 17 Apr 2020 11:02:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to;
        bh=W2UIL731ms6H2749NubZBGukRGojf/YJYQJMhF/P8E8=;
        b=jPldIo+7B9fgS62XviUd/0JrtTF4Fo1PN/aFMfYLnw6gPz0hX3JV44/fJyPGLxaTfR
         xR0EVjXWgYBWT4BS81vI5ljN/HZfP8kiR6n/Oo4EzzCqaeRh8N9ZBq22Cwy8x6sRsMCO
         iVUrPqHtUWTKlSiHPiE5sb4s7UNNS3NC42hG7qw/iznw+F2RXKGYltu/GolOwXU/Af4Z
         vtgAw7pQ3Z4brX27sVkbp9JIqCJTXsW3VBefplO8/H3iSY5y9U06CqxYx3XL6mfULtjT
         kx7yEC56Gm28fQu8UHuEIHSjANjpdKPCNG31FQJazdFuZgscXT0pvjsEJpPJHp4D4A5P
         BMuQ==
X-Gm-Message-State: AGi0PuYCLYo5Ns9LqkCCWHZafRfz8ZIlFzvgzDqTSvveYD4wwZgdLnJC
	DSX+MGvu+/vuwdQNWNIQduOr5OIFT36zSzkN0ro=
X-Google-Smtp-Source: APiQypKhuD+uOgR9rrS0DQv3xrbJBKy16J0okhitzwTpXXVMu2km+uT9wCXapmPlFzX+88BCnmAd8xO0p7NDG6VGHvQ=
X-Received: by 2002:a5b:84c:: with SMTP id v12mr7831549ybq.483.1587146577967;
 Fri, 17 Apr 2020 11:02:57 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <ae83255d-c9ca-fab9-d0f1-cd3325e720f2@baur-itcs.de>
From: Ulrich Sibiller <uli42@gmx.de>
Date: Fri, 17 Apr 2020 20:02:31 +0200
Message-ID: <CANVnVYJTBAXpuboCLDzXhPW_7AFVktSUtkuFzDxX2h-15xPTow@mail.gmail.com>
To: Stefan Baur <X2Go-ML-1@baur-itcs.de>, 1458@bugs.x2go.org
Content-Type: text/plain; charset="UTF-8"

On Fri, Apr 17, 2020 at 4:50 PM Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
>
> Am 17.04.20 um 16:24 schrieb Ulrich Sibiller:
> > I think it is a totally wrong approach to fiddle with nscd. Creating a
> > group using system tools should take of that already. If not it's a
> > bug, I'd say.
>
> LOL.  nscd caching the wrong(TM) things at the wrong(TM) time is an
> issue that's probably as old as Unix (or at least nscd) itself.  If you
> take a look at the postinst script in question, you will see that it
> does, in fact, use the system tools to add the group.  Still, it is
> neccesary to flush the cache or things have a tendency to go wrong.

Well, if you go that route there are more things to take into account:
- is nscd properly configured to cache groups at all?
- is there a distro-tool available for configuring/flushing/handling nscd
- are the multiple versions of nscd around? Which one to take?
- probably more
- what happens if a newer version of nscd is around that needs to be
called otherwise
- waht happens if the nscd binary is something completely different
and just happens to have the same name?
- same for ssd
- same for ANY other caching mechanism you might not even know

All these things tend to break sooner or later. That's the reason why
you should not do this in an installation script but report a bug
instead. This must be fixed at distro level.

Are you aware of any installation postscripts other than x2go that
handle nscd problems?

> > Besides: what about sssd that can also cache groups?
>
> That's a more interesting question, and we might have to add a check for
> it as well.  But as of right now, sssd being installed in combination
> with x2gobroker-ssh during a preseeded installation won't break anything.

I have seen the weirdest problems with sssd (and nscd as well). An I
still have one bug open at redhat for more  than year which redhat has
not fixed yet...

While you can work around such problems in local (site) scripts or as
local administrator you should NOT include such workaround in release
packages.

Uli

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:11:50 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.