sts-sponsors team mailing list archive

[Launchpad Bug Tracker <1766872@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug by Eric Desrochers (slashd):

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.

** Affects: friendly-recovery (Ubuntu)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: In Progress

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: Won't Fix

** Affects: friendly-recovery (Ubuntu Xenial)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: Confirmed

** Affects: systemd (Ubuntu Xenial)
     Importance: Undecided
         Status: Won't Fix

** Affects: friendly-recovery (Ubuntu Bionic)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: Confirmed

** Affects: systemd (Ubuntu Bionic)
     Importance: Undecided
         Status: Won't Fix

** Affects: friendly-recovery (Ubuntu Cosmic)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: In Progress

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

** Affects: friendly-recovery (Ubuntu Dd-series)
     Importance: Medium
     Assignee: Eric Desrochers (slashd)
         Status: Confirmed

** Affects: systemd (Ubuntu Dd-series)
     Importance: Undecided
         Status: Won't Fix


** Tags: id-5afda46ded21519fcf26f22b rls-bb-incoming sts
-- 
'Enable Network' in recovery mode not working properly.
https://bugs.launchpad.net/bugs/1766872
You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.