Bug#728422: [buildd-tools-devel] Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

[Antonio Terceiro]

On Wed, Apr 27, 2016 at 08:53:54PM +0200, Jérémy Lal wrote:
> Package: sbuild
> Version: 0.68.0-1
> Followup-For: Bug #728422
> 
> Maybe the problem comes simply from the fact that i booted
> on linux image 4.5 today, and booting on linux image 4.4.6
> makes it work again.
> Something with my config ?
> 
> [sid-amd64-sbuild]
> aliases=sid
> type=directory
> union-type=overlay
  ^^

this is known to be a problem with Linux 4.5 (#821442). It is fixed in
Linux 4.6


signature.asc
Description: PGP signature

Bug#728422: [buildd-tools-devel] Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

[Johannes Schauer]

Hi,

Quoting Jérémy Lal (2016-04-27 17:17:09)
> I reproduce the issue, same symptoms.

awesome!

Can you give me a step by step instruction which will allow me to reproduce the
issue on my system as well? As I said earlier, everything works on my system.
Thus, I need instructions how to get from zero to a chroot that exhibits the
behaviour you describe.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#728422: [buildd-tools-devel] Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

[Cyril Brulebois]

Hi,

answering in a linear fashion, but you may want to read the comment at
the bottom first… (see arrow: →)

Roger Leigh rle...@codelibre.net (2013-11-06):
 The failure is trying to run
 
   getent group sbuild  ${chroot}/etc/group
 
 However, this only works as root, and it's only used as a fallback
 in the unusual case that the passwd/group databases in the chroot
 are out of sync with the base system.  The real question here is
 why the system databases weren't copied over during the session
 setup.
 
 I would suggest trying to run schroot without sbuild and see that
 if you start a new session with
 
   schroot -b -n test -c sid-amd64-sbuild -v --debug=notice

I've recreated a new chroot (under systemd), named
experimental-amd64-sbuild, still using sid as the distribution.
sbuild-update -udcar experimental-amd64-sbuild fails the same way.

 and see if there is anything group-related in the output.

Let's see (21):
| kibi@arya:~$ grep -i group /tmp/schroot.log
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=type
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=active
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=run-setup-scripts
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=run-session-scripts
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=run-exec-scripts
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=profile
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=script-config
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=priority
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=aliases
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=environment-filter
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=description
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=users
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=groups
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=root-users
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=root-groups
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=mount-location
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=name
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=command-prefix
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=message-verbosity
| D(2): Getting keyfile group=experimental-amd64-sbuild, 
key=preserve-environment
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=shell
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=directory
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=location
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=personality
| D(2): Getting keyfile group=experimental-amd64-sbuild, 
key=user-modifiable-keys
| D(2): Getting keyfile group=experimental-amd64-sbuild, 
key=root-modifiable-keys
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=union-type
| D(2): Getting keyfile group=experimental-amd64-sbuild, key=union-mount-options
| D(2): Getting keyfile group=experimental-amd64-sbuild, 
key=union-overlay-directory
| D(2): Getting keyfile group=experimental-amd64-sbuild, 
key=union-underlay-directory
| D(2): Getting keyfile group=sid-amd64-sbuild, key=type
| D(2): Getting keyfile group=sid-amd64-sbuild, key=active
| D(2): Getting keyfile group=sid-amd64-sbuild, key=run-setup-scripts
| D(2): Getting keyfile group=sid-amd64-sbuild, key=run-session-scripts
| D(2): Getting keyfile group=sid-amd64-sbuild, key=run-exec-scripts
| D(2): Getting keyfile group=sid-amd64-sbuild, key=profile
| D(2): Getting keyfile group=sid-amd64-sbuild, key=script-config
| D(2): Getting keyfile group=sid-amd64-sbuild, key=priority
| D(2): Getting keyfile group=sid-amd64-sbuild, key=aliases
| D(2): Getting keyfile group=sid-amd64-sbuild, key=environment-filter
| D(2): Getting keyfile group=sid-amd64-sbuild, key=description
| D(2): Getting keyfile group=sid-amd64-sbuild, key=users
| D(2): Getting keyfile group=sid-amd64-sbuild, key=groups
| D(2): Getting keyfile group=sid-amd64-sbuild, key=root-users
| D(2): Getting keyfile group=sid-amd64-sbuild, key=root-groups
| D(2): Getting keyfile group=sid-amd64-sbuild, key=mount-location
| D(2): Getting keyfile group=sid-amd64-sbuild, key=name
| D(2): Getting keyfile group=sid-amd64-sbuild, key=command-prefix
| D(2): Getting keyfile group=sid-amd64-sbuild, key=message-verbosity
| D(2): Getting keyfile group=sid-amd64-sbuild, key=preserve-environment
| D(2): Getting keyfile group=sid-amd64-sbuild, key=shell
| D(2): Getting keyfile group=sid-amd64-sbuild, key=directory
| D(2): Getting keyfile group=sid-amd64-sbuild, key=location
| D(2): Getting keyfile group=sid-amd64-sbuild, key=personality
| D(2): Getting keyfile group=sid-amd64-sbuild, key=user-modifiable-keys
| D(2): Getting keyfile group=sid-amd64-sbuild, key=root-modifiable-keys
| D(2): Getting keyfile group=sid-amd64-sbuild, key=union-type
| D(2): Getting keyfile 

Bug#728422: [buildd-tools-devel] Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

[Roger Leigh]

On Fri, Nov 01, 2013 at 03:14:05AM +0100, Cyril Brulebois wrote:
 The last bit failed with:
 | D: Running command: schroot -d / -c 
 sid-amd64-sbuild-59d745d4-bd00-4c4d-82cb-1b21032d8205 --run-session -q -u 
 root -p -- getent group sbuild
 | /bin/sh: 1: cannot create 
 /var/lib/schroot/mount/sid-amd64-sbuild-59d745d4-bd00-4c4d-82cb-1b21032d8205/etc/group:
  Permission denied
 | E: Failed to create group sbuild
 | Failed to set up chroot
 
 Looking at the mount output, that reminded me I was running under
 systemd, so I wondered whether switching it off would help. And it
 helped indeed!
 
 I suspect there's some interference between some schroot things and
 systemd, but filing it against sbuild for now, since that's where I
 hit the bug so far.

The failure is trying to run

  getent group sbuild  ${chroot}/etc/group

However, this only works as root, and it's only used as a fallback
in the unusual case that the passwd/group databases in the chroot
are out of sync with the base system.  The real question here is
why the system databases weren't copied over during the session
setup.

I would suggest trying to run schroot without sbuild and see that
if you start a new session with

  schroot -b -n test -c sid-amd64-sbuild -v --debug=notice

and see if there is anything group-related in the output.
After this completes, is there a group file in the schroot
directory?  Does

  schroot -r -c test -- getent group sbuild

succeed or fail?

Does getent group sbuild work correctly on the base system when
systemd is running?  How about getent group?

sbuild and schroot don't really do anything which should be
affected by the init system in use.  Both just make use of
standard POSIX interfaces, and if systemd causes changes in
how these basic libc calls function, that's a bit worrying.
The schroot db copy is as simple as

  getent $db  $chroot/etc/$db

Any more information you could provide regarding the above would
be much appreciated.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org