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

[Eric Desrochers]

Public bug reported:

This bug has been introduced by 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

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.

** Affects: friendly-recovery (Ubuntu)
     Importance: High
         Status: New

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: sts

** Changed in: friendly-recovery (Ubuntu)
   Importance: Undecided => High

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

** Tags added: sts

-- 
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 introduced by 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

  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