[Bug 1726852] Re: 17.10 recovery root session networking failure

[Brian Murray]

** Package changed: ubuntu => friendly-recovery (Ubuntu)

-- 
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/1726852

Title:
  17.10 recovery root session networking failure

Status in friendly-recovery package in Ubuntu:
  New

Bug description:
  Hi,

  I just freshly installed a machine with the new 17.10 desktop, and
  after having trouble tried to fix that in a recovery root shell. When
  that did not help to fix the problem ( #1726842 ), I reinstalled with
  Lubuntu, which solved that problem for the moment.

  But with both, Ubuntu and Lubuntu, I ran into the problem that the
  recovery root shell is not working properly, it is not able to get the
  network running properly. It took me severe manual manipulation in
  /etc/network/interfaces and /etc/resolv.conf, to get the machine
  online. I've identified three problems.

  
  1. The machine tries to start the network through network-manager, which did not properly interact with systemd and it's nameserver at that state of boot process. Although the machine got an IP-address through DHCP, the configuration was not finished properly and aborted, due to some problem setting the DNS nameservers as passed from the DHCP server. 

  2. There's error messages that a grep would not work on
  /etc/resolv.conf, but I am not sure, where that error message came
  from. However, the /etc/resolv.conf is a link to
  ../run/systemd/resolve/stub-resolv.conf at that time, and the target
  does not exist at that time, so the link is dangling and every attempt
  to read, grep, write must fail.

  3. Another problem (and possibly the reason for 1 and 2) is that some
  startup scripts complain about the missing ifconfig command. Indeed,
  ifconfig is missing and not installed, I had to use ip to check the
  interface configuration. Probably someone has taken ifconfig out of
  standard installation, since ip is a full replacement and ifconfig
  outdated, but there's still scripts and programs that want to use
  ifconfig. Maybe that's why things go wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1726852/+subscriptions