Bug 1313130

Summary:	Satellite does not validate IP field when subnet set to static boot
Product:	Red Hat Satellite	Reporter:	madams
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DEFERRED	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.7	CC:	bkearney, nobody
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-28 20:46:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description madams 2016-03-01 03:14:16 UTC

Description of problem:

When provisioning a new host with a subnet that has Static selected as the default boot option, it is possible to leave the IP adddress field blank, but the rendered KS still attempts to configure the network device as Static but with an empty --ip= value.


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

Satellite 6.1.7

How reproducible:

Very

Steps to Reproduce:
1. Define Subnet
2. Define Default boot mode as static for Subnet
3. Build New Host
4. Select previously defined Subnet
5. Leave the IP address blank.
6. Submit new host build.

Actual results:

Host is "built" without an IP address.

Expected results:

Error when clicking on submit that requires field be filled out.

Comment 1 Bryan Kearney 2016-07-26 19:03:06 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2017-03-28 20:46:33 UTC

I do not see us addressing this in the next few releases. I am therefore closing this out. If you feel that this is a mistake, please feel free to re-open with additional information.