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

[John Spiller]

This has broken again in bionic.  While the fix is still in there, the
netcfg-common.c file that ubiquity uses does NOT handle the systemd-
resolve.service case, where the symlink is to ../run/systemd/resolv
/stub-resolv.conf, and so running ubiquity during oem-config-firstboot
again breaks the system.

-- 
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:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in netcfg source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released
Status in netcfg source package in Yakkety:
  Won't Fix
Status in netcfg source package in Zesty:
  Fix Released
Status in ubiquity source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This breaks oem-config installs because after running oem-config-firstboot, /etc/resolv.conf's symlink might be replaced by a regular file.

  [Test case]
  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.

  [Regression potential]
  This may regress by failing to recognize a case where resolvconf is not in use, or triggering a false-positive (resolvconf is not in use, by an install is tricked into thinking it is and removes resolv.conf). Corruption of /etc/resolv.conf or /run/resolvconf/resolv.conf should be considered as possible regressions from this SRU.

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