"activate networking" : broken from recovery mode

Bug #1580591 reported by dino99 on 2016-05-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
friendly-recovery (Ubuntu)

Bug Description

I have found that activating networking from the grub revovery mode is not possibLe.
So this mode is useless to update/upgrade/fix a broken intallation.
Maybe it is related to systemd not taking care of the feature.

Get that probLem with yakkety
ApportVersion: 2.20.1-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Tags: yakkety
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

dino99 (9d9) on 2016-05-11
summary: - "active network" broken from recovery mode
+ "activate network" broken from recovery mode
tags: added: systemd-boot
dino99 (9d9) on 2016-05-11
description: updated
tags: added: bot-stop-nagging
tags: added: yakkety
description: updated

apport information

tags: added: apport-collected
description: updated
dino99 (9d9) wrote : ProcEnviron.txt

apport information

Phillip Susi (psusi) on 2016-05-12
affects: grub2 (Ubuntu) → network-manager (Ubuntu)
dino99 (9d9) on 2016-05-12
summary: - "activate network" broken from recovery mode
+ "activate networking" : broken from recovery mode
tags: added: xenial
dino99 (9d9) wrote :

Also affect xenial

cat /etc/fstab

# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc1 during installation
UUID=aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa / ext4 errors=remount-ro 0 1
# /home was on /dev/sdc3 during installation
UUID=bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb /home ext3 defaults 0 2
# swap was on /dev/sdc2 during installation
UUID=cccccccc-cccc-cccc-cccc-cccccccccccc none swap sw 0 0

dino99 (9d9) wrote :

This has also been met by other users, like: http://ubuntuforums.org/showthread.php?t=2253852&p=13172673#post13172673

Looks like systemd is concerned here.

description: updated
dino99 (9d9) wrote :

Does not have that issue with Wily

Martin Pitt (pitti) on 2016-05-12
affects: systemd (Ubuntu) → friendly-recovery (Ubuntu)
no longer affects: network-manager (Ubuntu)
Martin Pitt (pitti) wrote :

I tested this on current xenial, and my ethernet interface does get configured via DHCP, through the "ifup -a", it's not yet getting to the NetworkManager fallback. I then commented out the "ifup -a" from /lib/recovery-mode/options/network and re-ran it, and NM gets brought up.

So I cannot reproduce this and I need more information what goes wrong for you. Please start recovery mode, select "root shell", and run

   sh -x /lib/recovery-mode/options/network > /var/tmp/network.debug 2>&1

Then reboot and attach /var/tmp/network.debug here. Thanks!

Changed in friendly-recovery (Ubuntu):
status: New → Incomplete
dino99 (9d9) wrote :

Tested the command with both xenial & yakkety 64 bits:

- after validating the command, i got dropped back to a frozen recovery menu
- ctrl+alt+del to exit after a while
- check nautilus , and cant find a network.debug output

- the command immediatly abort with: 'read only system'
- starting that command with 'sudo' does not help either.

So in both cases, it lokks like a right issue

Launchpad Janitor (janitor) wrote :

[Expired for friendly-recovery (Ubuntu) because there has been no activity for 60 days.]

Changed in friendly-recovery (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers