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

[Eric Desrochers]

We made some progress last week about this bug. We should be able to
push the changes into bzr soon, and then start testing. Once the testing
feedback are positive, we will then start SRU'ing the fix.

- Eric

** Also affects: friendly-recovery (Ubuntu Dd-series)
   Importance: Undecided
       Status: New

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

** Also affects: friendly-recovery (Ubuntu Bionic)
   Importance: Undecided
       Status: New

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

** Also affects: friendly-recovery (Ubuntu Cosmic)
   Importance: High
       Status: Confirmed

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
       Status: Won't Fix

** Changed in: systemd (Ubuntu Bionic)
       Status: New => Won't Fix

** Changed in: systemd (Ubuntu Dd-series)
       Status: New => Won't Fix

** Changed in: friendly-recovery (Ubuntu Dd-series)
       Status: New => Confirmed

** Changed in: friendly-recovery (Ubuntu Bionic)
       Status: New => Confirmed

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

** Changed in: friendly-recovery (Ubuntu Dd-series)
   Importance: Undecided => Medium

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

** Changed in: friendly-recovery (Ubuntu Bionic)
   Importance: Medium => Low

** Changed in: friendly-recovery (Ubuntu Dd-series)
   Importance: Medium => Low

** Changed in: friendly-recovery (Ubuntu Cosmic)
   Importance: Medium => Low

-- 
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:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Confirmed
Status in systemd source package in DD-Series:
  Won't Fix

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