Bug 216320

Summary:	Gateway required for NFS installation but value given not checked
Product:	Red Hat Enterprise Linux 5	Reporter:	Dirk Gfroerer <dirk.gfroerer>
Component:	anaconda	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-24 20:39:05 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:

Description Dirk Gfroerer 2006-11-19 08:35:34 UTC

Description of problem:


RHEL 5 Client Beta on x86_64


How reproducible:


Steps to Reproduce:
1. Download Beta2 for RHEL 5
2. Burn boot.iso on CD. Boot from CD.
3. Deselect DHCP and IPv6
4. In textual network screen you're informed you have to specify a valid gateway.
5. Not useful for me, since the machines don't have a gateway and will never
have (common case for many servers and also all client machines do have to use
proxies).
6. Don't fill in gateway information (i.e. leave blank).
7. Continue to next screen enter NFS install information.
8. Click next.
  
Actual results:
Error message showing up, indicating the NFS volumne cannot be mounted. No
access is being made to the NFS server. Machine on which RHEL 5 Beta 2 is being
installed is not "ping"-able.

Expected results:
Preferred would be to be able to install RHEL 5 Beta 2 without having to specify
a gateway, since as stated above not every machine will do have one.
Also acceptable would be an error message stating a gateway needs to be
specified or next button would be blocked as long as not all required
information was given.

Comment 1 David Cantrell 2007-07-24 20:39:05 UTC

This is currently fixed in RHEL 5.1 nightly builds, so I'm closing it.