Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionOrion Poplawski
2010-09-24 14:54:01 UTC
Description of problem:
Doing PXE/kickstart install. IP assigned via DHCP. In %post:
+ cat /etc/resolv.conf
search cora.nwra.com
+ mkdir -p /data/backup
+ mount -v -o nolock,vers=3 saga:/export/backup /data/backup
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: Failed to resolve server saga: Temporary failure in name resolution
Version-Release number of selected component (if applicable):
13.21.56
I am using Scientific Linux 6 so I don't know how useful this comment will be.
I am seeing the same problem. When NetworkManger first configures the network interface all is well. At sum point during the install the file is replaced with one that has a single line "search <domain>". As far as I can tell the only log that I can see when this happens is looks like:
<29> Arp 6 06:40:49 NetworkManager[542]: ifcfg-rh:
updating /etc/sysconfig/network-scripts/ifcfg-eth0
at that point /etc/sysconfig/network-scripts/ifcfg-eth0 changes and gets
an NM_CONTROLLED="yes" added to it and the /etc/resolv.conf file is
replaced with the single lined one.
I can send you the logs if you would like.
I am using spacewalk if that makes any difference.
I got the same problem (but also on SL6). I will try to reproduce with RHEL6, but this might take a while.
I also think that Network Manager on a server is a bad idea. I am not sure if it is a good idea to have it during the installation with anaconda.
Can you please check with RHEL 6.1? The one-line /etc/resolv.conf used to be written by anaconda at the end of the install. Since 6.1 anaconda doesn't touch the file (bug #687953).
Comment 7RHEL Program Management
2011-10-07 15:58:22 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.