Bug 719578 - misleading error message about ipv4 prefix when manually setting network configuration for network install in boot.iso
Summary: misleading error message about ipv4 prefix when manually setting network conf...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 726828
TreeView+ depends on / blocked
 
Reported: 2011-07-07 11:44 UTC by Jason Hird
Modified: 2018-11-14 11:42 UTC (History)
2 users (show)

Fixed In Version: anaconda-11.1.2.245-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 05:38:21 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0197 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2012-02-20 14:54:06 UTC

Description Jason Hird 2011-07-07 11:44:40 UTC
Description of problem:

When attempting to manually configure network settings to perform an NFS install of RHEL5.6 and RHEL5.7, the dialog asks for prefix but states that a dotted decimal address is acceptable. If you provide a dotted decimal netmask you get an error: "Prefix must be between 1 and 32 for IPv4 networks or between 1 and 128 for IPv6 networks"


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


How reproducible:
100%

Steps to Reproduce:
1.Boot a system with a RHEL5.6 or RHEL5.7 boot iso
2.Select language and keyboard, and NFS install.
3.Choose to configure network manually.
4.Disable IPv6
5.Enter IP address (example 192.168.122.250)
6.Tab to next field and enter dotted decimal netmask (example: 255.255.255.0)
7.Tab to next field.

You are presented with a misleading error message:
"Prefix must be between 1 and 32 for IPv4 networks or between 1 and 128 for IPv6 networks"

However if you complete the rest of the form, and ignore the error message, the network is still successfully configured, and will install from the NFS server.
  
Actual results:
You get an error even though the entered data is valid

Expected results:
Installer should recognise that the entered netmask is valid and not show an error.

Additional info:

Comment 1 Radek Vykydal 2011-07-07 15:21:00 UTC
For rawhide this was fixed in bug #243250. We could port the patch to RHEL 5.

Comment 4 RHEL Program Management 2011-08-05 12:30:27 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 7 Radek Vykydal 2011-09-29 13:53:42 UTC
This should be fixed in anaconda-11.1.2.245-1 with commit f79c0375ea2e69b4a77f0b79d43942170310d7a4.

Comment 9 Radek Vykydal 2011-09-29 14:49:45 UTC
I am working on creation of the special initrd.img for rhel 5.6. Hopefully I'll be able to deliver it for testing within couple of days.

Comment 11 Radek Vykydal 2011-10-03 14:29:04 UTC
The initrd.img for RHEL 5.6 is here:
http://rvykydal.fedorapeople.org/initrd.719578.img
I only checked locally that the fix works and 5.6 installs using the image.

Comment 13 Alexander Todorov 2011-12-02 14:45:29 UTC
(In reply to comment #0)
> Steps to Reproduce:
> 1.Boot a system with a RHEL5.6 or RHEL5.7 boot iso
> 2.Select language and keyboard, and NFS install.
> 3.Choose to configure network manually.
> 4.Disable IPv6
> 5.Enter IP address (example 192.168.122.250)
> 6.Tab to next field and enter dotted decimal netmask (example: 255.255.255.0)
> 7.Tab to next field.
>

With anaconda-11.1.2.248 there's no error message when Tabbing to the next field. I tried with a prefix of 24 and 255.255.255.0. Both worked fine.

Comment 14 errata-xmlrpc 2012-02-21 05:38: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-0197.html

Comment 15 Red Hat Bugzilla 2013-10-04 00:25:09 UTC
Removing external tracker bug with the id 'DOC-59262' as it is not valid for this tracker


Note You need to log in before you can comment on or make changes to this bug.