[Bug 1646585] Re: oem-config replaces /etc/resolv.conf symlink with a hard file

[Mathieu Trudel-Lapierre]

Seems like the most sensible fix is in netcfg after all; we should apply
the patch (minus the ubiquity bits), after properly testing that this
doesn't break server installs with only d-i, and that it doesn't break
non-OEM ubiquity installs.

** Changed in: ubiquity (Ubuntu Zesty)
    Milestone: ubuntu-17.04 => None

** Also affects: netcfg (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: netcfg (Ubuntu Zesty)
       Status: New => Triaged

** Changed in: netcfg (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: netcfg (Ubuntu Zesty)
     Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/1646585

Title:
  oem-config replaces /etc/resolv.conf symlink with a hard file

Status in Nvidia:
  New
Status in netcfg package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in netcfg source package in Zesty:
  Triaged
Status in ubiquity source package in Zesty:
  Triaged

Bug description:
  The DGX server install process uses oem-config to setup certain
  settings.  We are seeing that oem-config-firstboot is replacing the
  /etc/resolv.conf symlink to /run/resolvconf/resolv.conf with a hard
  file at /etc/resolv.conf.

  This was confirmed by booting in single user mode after a fresh
  install, and seeing the symlink is still there.  Then go thru oem-
  config-firstboot, and find that the symlink is no longer there when
  that is done.

  We have to run "sudo dpkg-reconfigure resolvconf" to restore that
  symlink.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia/+bug/1646585/+subscriptions