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.
Bug 797108 - DNS server changed unexpectedly even without change on the TUI
Summary: DNS server changed unexpectedly even without change on the TUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 09:48 UTC by shine
Modified: 2016-04-26 14:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When configuring the Hypervisor to use DHCP, previously configured DNS server entries would be wiped out. Now, the previously configured servers are kept.
Clone Of:
Environment:
Last Closed: 2012-07-19 14:19:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Description shine 2012-02-24 09:48:52 UTC 
Description of problem:
DNS server changed unexpectedly.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120215.0.el6

How reproducible:
100%

Steps to Reproduce:
1. Configure eth0 with dhcp, DNS server is blank, use arrow keys switch to "status" page and back to "network",it's 10.66.127.10 now. (bug 746180)
2. Change DNS server to 10.66.104.210 and apply, it still show 10.66.127.10 both in tui and /etc/resolv.conf.
3. Change DNS server to 10.66.104.210 again and apply, it is 10.66.104.210 both in tui and /etc/resolv.conf.
4. Configure the eth0 with dhcp again, DNS server displayed 10.66.104.210, but in /etc/resolv.conf it's 10.66.127.10, use arrow keys switch to "status" page and back to "network", it's 10.66.127.10. (bug 746180)
5. Do not change anything and apply on the network page. the DNS server changed from 10.66.127.10 to 10.66.104.210.
6. Do not change anything and apply on the network page. The DNS server changed from 10.66.104.210 to 10.66.127.10
7. repeat press the apply button, dns server is altering between them.
  
Actual results:
DNS server changed unexpectedly after some configure actions.

Expected results:
DNS server should not change if user does not change it on TUI.
Comment 3 Guohua Ouyang 2012-04-17 02:53:03 UTC 
verified on 6.3-20120411.1 build, the DNS server always displayed what you have changed.

move the bug to status "verified".
Comment 4 Mike Burns 2012-06-13 16:54:35 UTC 
    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 using DHCP, a previously configured DNS server would be wiped out.  Now, the previously configured server is honored and kept correctly.
Comment 5 Stephen Gordon 2012-06-13 21:52:55 UTC 
    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 using DHCP, a previously configured DNS server would be wiped out.  Now, the previously configured server is honored and kept correctly.+When configuring the Hypervisor to use DHCP, previously configured DNS server entries would be wiped out. Now, the previously configured servers are kept.
Comment 7 errata-xmlrpc 2012-07-19 14:19:21 UTC 
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-0741.html
Note You need to log in before you can comment on or make changes to this bug.