[Bug 1646585] Re: oem-config replaces /etc/resolv.conf symlink with a hard file
Chris J Arges
1646585 at bugs.launchpad.net
Wed May 24 10:41:21 UTC 2017
Hello Newton, or anyone else affected,
Accepted netcfg into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/netcfg/1.135ubuntu4.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: netcfg (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Tags added: verification-needed
--
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 Committed
Status in ubiquity source package in Xenial:
Triaged
Status in netcfg source package in Zesty:
Fix Released
Status in ubiquity source package in Zesty:
Fix Released
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
More information about the foundations-bugs
mailing list