Indeed, ubiquity has not been updated yet, because we should be able to verify netcfg without it. Nevertheless, I have another SRU to land that also needs to be applied to xenial, so I'll upload ubiquity along as soon as netcfg lands in xenial-proposed.
** Description changed: - 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. + [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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646585 Title: oem-config replaces /etc/resolv.conf symlink with a hard file To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1646585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
