[Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

beta-tester 1755863 at bugs.launchpad.net
Thu Feb 14 18:13:41 UTC 2019


@Guillermo, i have the same issue with ubuntu 19.04 daily (pending) from 2019-02-14
(without using the workaround) when pxe booting.
/var/log/syslog shows the folowing lines, when i serch for resolv:
```
Feb 14 17:53:27 ubuntu systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Feb 14 17:53:27 ubuntu systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
Feb 14 17:53:27 ubuntu avahi-daemon[1225]: Failed to open /etc/resolv.conf: Invalid argument
Feb 14 17:53:27 ubuntu kernel: [    6.498832] Key type dns_resolver registered
Feb 14 17:53:27 ubuntu kernel: [    6.985154] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:27 ubuntu kernel: [    6.985719] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:27 ubuntu kernel: [    6.986106] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:27 ubuntu kernel: [    6.988112] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:27 ubuntu kernel: [    7.347354] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:27 ubuntu kernel: [    7.357711] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Feb 14 17:53:28 ubuntu sh[1400]: grep: /etc/resolv.conf: No such file or directory
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Positive Trust Anchors:
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 19036 8 2 ...
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 20326 8 2 ...
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Using system hostname 'ubuntu'.
Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 14 17:53:30 ubuntu NetworkManager[1405]: <info>  [1550166810.1729] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: netplan.conf) (etc: default-wifi-powersave-on.conf)
Feb 14 17:53:30 ubuntu NetworkManager[1405]: <info>  [1550166810.4138] dns-mgr[0x55dc42397170]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
Feb 14 17:54:29 ubuntu systemd-resolved[1604]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
```

PS: long time ago i opened a report for that, but never got any reaction there...
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1755863

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Triaged
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root at iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root at iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root at iscsi-bionic:/home/ubuntu# mount | grep test
  root at iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
     Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago
  root at iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
     Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root at iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root at iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
     Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root at iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root at iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root at iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
     Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root at iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root at iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root at iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root at iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
     Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago
  root at iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root at iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root at iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
     Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago
  root at iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root at iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root at iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root at iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root at iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1755863/+subscriptions



More information about the Ubuntu-sponsors mailing list