[Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

[Eric Desrochers]

I did some progress...

I was able to make a few 'enabled|static' services to start such as :
dbus.socket
networking.service
system-resolved.service

NetworkManger doesn't seems to start well.

By making the following changes :

# /lib/recovery-mode/options/network
--------------------------------------
if [ -d /run/systemd/system ]; then
-    for i in dbus.socket systemd-resolved.service networking.service systemd-networkd.service NetworkManager.service; do
+    for i in dbus.socket networking.service systemd-networkd.service systemd-resolved.service NetworkManager.service; do
-        systemctl is-enabled -q $i && systemctl start $i
+        systemctl is-enabled -q $i && systemctl --job-mode=ignore-dependencies --no-ask-password start $i
    done
    /lib/systemd/systemd-networkd-wait-online && exit 0
fi
--------------------------------------

* Changed the order to start systemd-resolved.service as mentioned in:

# /lib/systemd/system/systemd-resolved.service
After=systemd-networkd.service network.target

to be after systemd-networkd.service

* Add "--no-ask-password" to avoid systemd-tty-ask-password-agent to block
* Add "--job-mode=ignore-dependencies" has most of the service are not running and waiting.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1766872

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
          |-recovery-menu---network---systemctl---systemd-tty-ask
          |-systemd-journal
          ....

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service                 start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target                 start waiting
  3 basic.target                   start waiting
  .....

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions