Debian Bug report logs - #917633
udisk2 post-installation fails in chrooted environments

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Alf Gaida <agaida@siduction.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 16:28:34 +0100

Package: udisks2
Version: 2.8.1-3
Severity: important

Dear Maintainer,

tried to install udisks2 in a chroot:

Setting up udisks2 (2.8.1-3) ...
Failed to scan devices: No such file or directory
dpkg: error processing package udisks2 (--configure):
 installed udisks2 package post-installation script subprocess returned error exit status 1

Noticed the chroot check for udev and wonder about if a check would be helpful here too.

Cheers Alf 

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.20.0-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages udisks2 depends on:
ii  dbus                   1.12.12-1
ii  libacl1                2.2.52-3+b1
ii  libatasmart4           0.19-5
ii  libblockdev-fs2        2.20-6
ii  libblockdev-loop2      2.20-6
ii  libblockdev-part2      2.20-6
ii  libblockdev-swap2      2.20-6
ii  libblockdev-utils2     2.20-6
ii  libblockdev2           2.20-6
ii  libc6                  2.28-4
ii  libglib2.0-0           2.58.1-2
ii  libgudev-1.0-0         232-2
ii  libmount1              2.33-0.2
ii  libpam-systemd         240-2
ii  libpolkit-agent-1-0    0.105-23
ii  libpolkit-gobject-1-0  0.105-23
ii  libsystemd0            240-2
ii  libudisks2-0           2.8.1-3
ii  parted                 3.2-23
ii  udev                   240-2

Versions of packages udisks2 recommends:
ii  dosfstools           4.1-2
ii  e2fsprogs            1.44.5-1
ii  eject                2.1.5+deb1+cvs20081104-13.2
ii  exfat-utils          1.3.0-1
ii  libblockdev-crypto2  2.20-6
ii  ntfs-3g              1:2017.3.23AR.3-2
ii  policykit-1          0.105-23

Versions of packages udisks2 suggests:
ii  btrfs-progs          4.19.1-1
pn  f2fs-tools           <none>
ii  libblockdev-mdraid2  2.20-6
ii  mdadm                4.1~rc1-4
pn  nilfs-tools          <none>
ii  reiserfsprogs        1:3.6.27-3
pn  udftools             <none>
pn  udisks2-bcache       <none>
ii  udisks2-btrfs        2.8.1-3
ii  udisks2-lvm2         2.8.1-3
pn  udisks2-vdo          <none>
pn  udisks2-zram         <none>
ii  xfsprogs             4.15.1-1

-- no debconf information

Message #10 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Alf Gaida <agaida@siduction.org>, 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 16:42:34 +0100

Am 29.12.18 um 16:28 schrieb Alf Gaida:
> Package: udisks2
> Version: 2.8.1-3
> Severity: important
> 
> Dear Maintainer,
> 
> tried to install udisks2 in a chroot:
> 
> Setting up udisks2 (2.8.1-3) ...
> Failed to scan devices: No such file or directory
> dpkg: error processing package udisks2 (--configure):
>  installed udisks2 package post-installation script subprocess returned error exit status 1

> Noticed the chroot check for udev and wonder about if a check would be helpful here too.

Keep in mind that deb-systemd-invoke respects policy-rc.d and a build
chroot should normally have setup policy-rc.d to not start any services.

And if you try to run systemctl directly inside a chroot you should get
something like this
# systemctl start udisks2
Running in chroot, ignoring request: start

So I'm not quite sure why it fails for you.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Message #15 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Alf Gaida <agaida@siduction.org>

To: 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 17:05:51 +0100

On 29.12.18 16:42, Michael Biebl wrote:
> Keep in mind that deb-systemd-invoke respects policy-rc.d and a build
> chroot should normally have setup policy-rc.d to not start any services.
> 
> And if you try to run systemctl directly inside a chroot you should get
> something like this
> # systemctl start udisks2
> Running in chroot, ignoring request: start
> 
> So I'm not quite sure why it fails for you.
> 

Maybe i wasn't clear enough - i didn't try anything in that regard, i
only tried to install the package within an iso build. With the
unmodified udisk2 package the result in the log was:

Setting up libhttp-daemon-perl (6.01-1) ...
Setting up udisks2 (2.8.1-3) ...
Failed to scan devices: No such file or directory
dpkg: error processing package udisks2 (--configure):
 installed udisks2 package post-installation script subprocess returned
error exit status 1
Setting up aptitude (0.8.11-6) ...

after a quick and really dirty modification:

diff --git a/debian/udisks2.postinst b/debian/udisks2.postinst
index 0dcf95b..381cd96 100644
--- a/debian/udisks2.postinst
+++ b/debian/udisks2.postinst
@@ -4,7 +4,7 @@ set -e

 if [ "$1" = "configure" ]; then
     # we ship udev rules, so trigger an update
-    udevadm trigger --subsystem-match=block --action=change
+    udevadm trigger --subsystem-match=block --action=change | true

 fi

the installation result looks like this:

Setting up libhttp-daemon-perl (6.01-1) ...
Setting up udisks2 (2.8.1-3.1) ...
Failed to scan devices: No such file or directory
Created symlink
/etc/systemd/system/graphical.target.wants/udisks2.service ->
/lib/systemd/system/udisks2.service.
Setting up aptitude (0.8.11-6) ...

So it seems that the udevadm trigger is the culprit

Cheers Alf

Message #20 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Alf Gaida <agaida@siduction.org>

To: 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 18:54:34 +0100

Additional: «Installing in a chroot should not fail because udevadm
trigger in postinst». https://bugs.debian.org/917642

Changed behaviour of udevadm?

Message #25 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Alf Gaida <agaida@siduction.org>, 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 18:54:52 +0100

[Message part 1 (text/plain, inline)]

Am 29.12.18 um 17:05 schrieb Alf Gaida:
>  if [ "$1" = "configure" ]; then
>      # we ship udev rules, so trigger an update
> -    udevadm trigger --subsystem-match=block --action=change
> +    udevadm trigger --subsystem-match=block --action=change | true
> 
>  fi

I guess you meant "||" here.

That seems like a reasonable change. Do you want to file a MR for that?

[signature.asc (application/pgp-signature, attachment)]

Message #30 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Alf Gaida <agaida@siduction.org>

To: 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 18:59:14 +0100

[Message part 1 (text/plain, inline)]

On 29.12.18 18:54, Michael Biebl wrote:
> I guess you meant "||" here.
> 
> That seems like a reasonable change. Do you want to file a MR for that?
> 

Yes - otherwise it would be cool to know the reason for the change in
behaviour.

[signature.asc (application/pgp-signature, attachment)]

Message #35 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Alf Gaida <agaida@siduction.org>, 917633@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Sat, 29 Dec 2018 19:26:31 +0100

Am 29.12.18 um 18:59 schrieb Alf Gaida:
> On 29.12.18 18:54, Michael Biebl wrote:
>> I guess you meant "||" here.
>>
>> That seems like a reasonable change. Do you want to file a MR for that?
>>
> 
> Yes - otherwise it would be cool to know the reason for the change in
> behaviour.

Quickly glancing at the systemd v240 changelog I don't see any mention
of a changed udevadm behaviour. So I'm not sure if it's deliberate or
not (fwiw I actually haven't tested if v239 behaves differently)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Message #40 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bicha <jbicha@debian.org>

To: 917633@bugs.debian.org

Cc: Alf Gaida <agaida@siduction.org>, Michael Biebl <biebl@debian.org>

Subject: Re: [Pkg-utopia-maintainers] Bug#917633: Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Fri, 4 Jan 2019 10:20:55 -0500

Control: affects -1 src:gvfs src:gnome-disk-utility
Control: tags -1 +patch

This issue was detected by piuparts and is blocking migration to
Testing for gnome-disk-utility and gvfs.

I see that there is a MR now:
https://salsa.debian.org/utopia-team/udisks2/merge_requests/2

References
----------------
https://piuparts.debian.org/sid/source/g/gnome-disk-utility.html
https://piuparts.debian.org/sid/source/g/gvfs.html

Thanks,
Jeremy Bicha

Message #51 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: Jeremy Bicha <jbicha@debian.org>, 917633@bugs.debian.org

Cc: Alf Gaida <agaida@siduction.org>, Michael Biebl <biebl@debian.org>

Subject: Re: Bug#917633: udisk2 post-installation fails in chrooted environments

Date: Tue, 08 Jan 2019 12:48:39 -0800

[Message part 1 (text/plain, inline)]

Control: affects 917633 src:ltsp

Also blocking migration for ltsp:

  https://piuparts.debian.org/sid/fail/ltsp-server-standalone_5.18.12-1.log

live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #58 received at 917633@bugs.debian.org (full text, mbox, reply):

From: Ulrike Uhlig <ulrike@debian.org>

To: 917633@bugs.debian.org

Subject: Also blocks migration of tails-installer

Date: Tue, 08 Jan 2019 20:54:00 +0000

Hello!

this issue currently also blocks the migration of tails-installer,
shortly before the freeze.

Cheers!
u.

Message #67 received at 917633-submitter@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 917633-submitter@bugs.debian.org

Subject: Bug #917633 in systemd marked as pending

Date: Tue, 08 Jan 2019 21:13:57 +0000

Control: tag -1 pending

Hello,

Bug #917633 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/systemd-team/systemd/commit/b89ae41a352f37f60918fb65efd6f7c71503ff5e

------------------------------------------------------------------------
udevadm: Refuse to run trigger, control, settle and monitor commands in chroot

Closes: #917633
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917633

Message #74 received at 917633-close@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 917633-close@bugs.debian.org

Subject: Bug#917633: fixed in systemd 240-3

Date: Wed, 09 Jan 2019 19:10:19 +0000

Source: systemd
Source-Version: 240-3

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 917633@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Jan 2019 18:40:57 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current hostname
 libnss-mymachines - nss module to resolve hostnames for local container instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd    - system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 917633 917948 918190 918658
Changes:
 systemd (240-3) unstable; urgency=medium
 .
   * udev.init: Trigger add events for subsystems.
     Update the SysV init script and mimic the behaviour of the initramfs and
     systemd-udev-trigger.service which first trigger subsystems and then
     devices during the coldplug stage.
   * udevadm: Refuse to run trigger, control, settle and monitor commands in
     chroot (Closes: #917633)
   * network: Set link state configuring before setting addresses.
     Fixes a crash in systemd-networkd caused by an assertion failure.
     (Closes: #918658)
   * libudev-util: Make util_replace_whitespace() read only len characters.
     Fixes a regression where /dev/disk/by-id/ names had additional
     underscores.
   * man: Update color of journal logs in DEBUG level (Closes: #917948)
   * Remove old state directory of systemd-timesyncd on upgrades.
     Otherwise timesyncd will fail to update the clock file if it was created
     as /var/lib/private/systemd/timesync/clock.
     This was the case when the service was using DynamicUser=yes which it no
     longer does in v240. (Closes: #918190)
Checksums-Sha1:
 000af5cf85311dc55ebdb77bbf92b0d4b990583f 4898 systemd_240-3.dsc
 a863be34d8dc7d16d43c2e0e5d2a6c7378e8e86d 144236 systemd_240-3.debian.tar.xz
 3bc84e7b0406df9e437254ccc22ec846e511929d 9079 systemd_240-3_source.buildinfo
Checksums-Sha256:
 08aed1c24e5d22183674cef810c606f05cc2a38f3aee831263544738b4c50f3a 4898 systemd_240-3.dsc
 f8ffdcbcc26e80895f267fe82f4e9204bcb4e8aca36c4974452226baaa30213c 144236 systemd_240-3.debian.tar.xz
 821b478ec41fa4a5ea264b3ed84955b910bdeb5558f8c6d0fcd8b77b2b1228cb 9079 systemd_240-3_source.buildinfo
Files:
 0137ad308d713815f9c8e46be0d53253 4898 admin optional systemd_240-3.dsc
 c2d146e072783d01aa83f2a7cce2f48d 144236 admin optional systemd_240-3.debian.tar.xz
 1d1d476c3163c94a3a1ced391c98a67e 9079 admin optional systemd_240-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlw2Pb8ACgkQauHfDWCP
Itx8WQ/+OgrUoOJyz2kViRWD9/O2gzbfCAp8M/ryEqDM+Zd+vA/dfkOH2NvUrrJf
gBZany5TqPDHFeMndmpRfQFzyM3Yw6NtMOMj/yhLycc+BBxtv4CBeEejj0amJCnI
tNuyWR4VULQuV0zMlyTRXOTzk/Y3lhjhoJ+cdEU55eUbgfffw88BpFPPzc9cjz68
p2zu8ehxfiEpdtit5pPtQamP/obx5MHXevFd8rYxkyktJ8eG5JC73bZR91J38PVN
/V+U7zI0J6do0voSaURyPc4uHfMP7DxxKF2wrQ60Ue6r+iqA8SN2d7AhFIDnSr8e
GRs5Mf6OJlV3iZe0m1MgEjXlXtBzWezS8WEGA8GBC0zIELPoJMH6lW5JelGs65Ej
W9Rz/cAwiZYE1OtUT8jHKUHwS+V3GsSdQmGMEEsA6045Gt+h4amz/cu2fMetYKD7
BtyrZjczeGpY1NikchACGZ04DULMcoC9eStVY0LxkdhQzTs6Brj3dlapH/oFG6tb
4CGBdayLcHb9CKM1zCeW6kdHzqJlh3fmkaKqQYqq7ifqIcB4BaUk9Sjb7kmb7hHv
J4GAEl6NEm8P6jDiWz10vYUSAhwar+NuM4mnpDS59jMVxct9buiSVUgPKSTRGZ43
moqGnygk1KSzl9Fv8uK3d2PhNUozOVMMvlq8DJf9SRFxvXSBe/w=
=J5uK
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.