Hide Forgot
This bug has been copied from bug #675325 and has been proposed to be backported to 5.7 z-stream (EUS).
Test only, no code change
Correct the verify steps as below, on build rhev-hypervisor-5.7-20120103.1: 1. on multi-nics machine, setup one nice and dns during install 2. after reboot, all other nics have "PEERDNS=no" in ifcfg-ethX. 3. add "BOOTPROTO=dhcp" in ifcfg-ethX and ifup them, /etc/resolv.conf is not changed. the bug is verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When the hypervisor was installed on a machine with multiple Network Interface Cards (NICs), and only one NIC wass configured at install time, the resolv.conf file would be overwritten each time a change was made to networking. The statement PEERDNS="no" is now added to all interface configuration (ifcfg*) files created by the hypervisor. This prevents the incorrect overwriting of the resolv.conf file.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When the hypervisor was installed on a machine with multiple Network Interface Cards (NICs), and only one NIC wass configured at install time, the resolv.conf file would be overwritten each time a change was made to networking. The statement PEERDNS="no" is now added to all interface configuration (ifcfg*) files created by the hypervisor. This prevents the incorrect overwriting of the resolv.conf file.+The /etc/resolv.conf file was being overwritten every time a change was made to networking. The statement PEERDNS="no" is now added to all interface configuration (ifcfg*) files created by the hypervisor. This prevents the incorrect overwriting of the resolv.conf file.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0015.html