Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 465175

Summary: Incorrect DNS format on s390 causes traceback
Product: Red Hat Enterprise Linux 4 Reporter: Brad Hinson <bhinson>
Component: anacondaAssignee: Dave Cantrell <dcantrell>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: high    
Version: 4.7CC: atodorov, borgan
Target Milestone: rc   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-18 20:16:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 465174    
Bug Blocks:    
Attachments:
Description Flags
Patch to sanity check DNS servers entered none

Description Brad Hinson 2008-10-01 22:09:36 UTC 
Created attachment 319170 [details]
Patch to sanity check DNS servers entered

+++ This bug was initially created as a clone of Bug #465174 +++

Created an attachment (id=319168)
Patch to sanity check DNS servers entered

Description of problem:
Problem discovered at customer site.  If DNS is specified in CONF or at console as " " (empty space) or ":" (colon with no addresses), anaconda dies with traceback:

The VNC server is now running.
Please connect to begin the install...
Starting graphical installation...
Traceback (most recent call last):
  File "/usr/bin/anaconda", line 1088, in ?
    id = instClass.installDataClass(extraModules, floppyDevice, configFileData, method)
  File "/usr/lib/anaconda/instdata.py", line 287, in __init__
    self.reset()
  File "/usr/lib/anaconda/instdata.py", line 60, in reset
    self.network = network.Network()
  File "/usr/lib/anaconda/network.py", line 204, in __init__
    self.primaryNS = resolv[1]
IndexError: list index out of range

To avoid this error, a properly formatted DNS address must be specified (either "" empty string, or one or more addresses separated by colon).  Anaconda should also have a sanity check on the DNS server(s) entered to avoid this traceback.

Version-Release number of selected component (if applicable):
anaconda-11.1.2.113-1

How reproducible:
100%

Steps to Reproduce:
1. Add either DNS=" " or DNS=":" to CMS CONF file on s390
2. Attempt any type of network install (NFS/HTTP/FTP), either graphical or text
3. Traceback occurs after entering install method, at the beginning of stage 2
Comment 1 Dave Cantrell 2008-12-10 01:49:04 UTC 
I'll give this a devel-ack.  Brad, can you provide a reproducer or some way for QA to test?
Comment 2 RHEL Program Management 2008-12-10 01:59:14 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 3 Brad Hinson 2008-12-10 18:17:40 UTC 
In response to comment 1:

To test, in the CONF file, specify either:

DNS=" "
(quote, empty space, quote)

or

DNS=":"
(quote, colon, quote)

Without patch, anaconda will traceback.
Comment 4 Dave Cantrell 2008-12-10 20:21:21 UTC 
Can we get a qa-ack or nak for this bug for 4.8?
Comment 5 Dave Cantrell 2008-12-16 00:01:33 UTC 
Patch committed to git repository, will be in anaconda-10.1.1.92-1.
Comment 10 errata-xmlrpc 2009-05-18 20:16:10 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0978.html