Bug#762953: no network after emergency mode

[Michael Biebl]

Control: tags -1 confirmed

Am 26.09.2014 um 15:28 schrieb Marc Haber:
> Given a system with a non-essential crypt disk, which should be
> unlocked on boot and mounted via /etc/fstab.
> 
> I then enter three times a wrong key and get dumped to emergency mode.
> In emergency mode, the network seems fine.
> 
> I then exit emergency mode and get prompted for the cryptdisk key
> again. This time, I enter the correct one, boot completes, and I can
> log in on the console, but find the network gone.

Afaics you are using ifupdown, specifically allow-hotplug interfaces to
start the network.
With a similar setup I can confirm your findings.
The ifup at eth0.service, which is triggered via udev, is active when
emergency mode is entered, but stopped when emergency mode is left.

> Is that intended behavior?

No, I would say it's not. Will need to check, if that is a general
problem for units triggered via udev rules.
E.g. I also noticed, that sound.target (which is also triggered via
udev) is also not active after exiting emergency mode.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140928/91cf56fc/attachment-0002.sig>