Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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:
Embargoed:


Attachments (Terms of Use)

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.