RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
After upgrading a RHEV-H node from 6.3 (RHEV Hypervisor - 6.3 - 20120910.0.rhev31.el6_3) to latest 6.4-20121126 (taken from BETA channel), the networking scripts are ignoring the DNS server option, affecting the normal fonctioning of the service because it refers to the RHEV manager using DNS name.

The problem is because the network-scripts are using PEERDNS=no. It should be "yes".

Version-Release number of selected component (if applicable):
6.4-20121126

How reproducible:
Upgrade from 6.3 (beta) to latest version (6.4-20121126).
Then restart the RHEV-H node, and DNS configuration is lost (no nameserver in /etc/resolv.conf)
If we fix the network-script (PEERDNS=yes), and do "service network restart", the dhcp-client sets again the nameserver in /etc/resolv.conf

Steps to Reproduce:
1.Upgrade to 6.4 RHEVH
2.Reboot
3.No DNS servers are then found in the system
  
Actual results:
DNS client stops working

Expected results:
DNS nameserver (setting /etc/resolv.conf) should work when using DHCP 

Additional info:
Maybe removing the interface configuration and re-enabling would fix it, but anyway, the upgrade process breaks the RHEVH config when using DHCP to setup the /etc/resolv.con nameserver.

Fixed this issue on build rhev-hypervisor6-6.4-20121206.0.el6.

*** This bug has been marked as a duplicate of bug 879498 ***