Bug 1313130 - Satellite does not validate IP field when subnet set to static boot
Summary: Satellite does not validate IP field when subnet set to static boot
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.1.7
Hardware: x86_64
OS: Linux
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 03:14 UTC by madams
Modified: 2019-09-26 13:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-28 20:46:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.