Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1194221

Summary: UI should set boot-modes appropriately under subnet
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: WebUIAssignee: Marek Hulan <mhulan>
WebUI sub component: Foreman QA Contact: Kedar Bidarkar <kbidarka>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: bkearney, jmontleo, sghai, tkolhar
Version: 6.1.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9547
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:25:18 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:
Bug Depends On:    
Bug Blocks: 1193987    

Description Kedar Bidarkar 2015-02-19 11:09:40 UTC
Description of problem:

unable to provision hosts unless boot mode is set to DHCP under subnet.

Provisioning of a "New Host" fails, while trying to fetch the file, 
http://xxxx.redhat.com/pulp/repos/Default_Organization/Dev/rhel66_cv/custom/RHEL6/RHEL66_x86_64/images/install.img

Possible reasons: network might not be configured properly.

Version-Release number of selected component (if applicable):
sat6.1 Beta snap3 compose2

How reproducible:
always

Steps to Reproduce:
1. create a subnet with "boot mode" set as "static".
2. And then try to provision a HOST.
3. 

Actual results:
Fetching the above mentioned file fails as, network might not be configured properly.

Expected results:
Should be able to provision Hosts successfully.

*) I assume, as many subnet setups would be with "DHCP", we need to have this option as default rather than "static" option.


Additional info:

As this is a new sat6.1 feature , we need this info added to release docs too and a TIP near the fields.

Comment 2 Marek Hulan 2015-02-24 10:06:41 UTC
tested, it works if dns nameserver and gateway is specified

Comment 3 Kedar Bidarkar 2015-02-24 10:31:59 UTC
spoke to marek hulan,


What is the purpose of IPAM field?

<mhulan> kbidarka: IPAM field only change behaviour of host form, whether the IP field is auto prefilled for you...


IPAM and boot-mode combinations:

If boot-mode: static then IPAM: Internal DB
If boot-mode: DHCP, then IPAM: DHCP

<mhulan> kbidarka: for boot mode static, usually internal DB makes most sense.
and none would be used if you want to assign IP manually.


For the fix at the WebUI level, 

a) I think if IPAM is set to DHCP, boot-mode should also be also set to "DHCP" automatically

b) or set the default value for boot-mode to DHCP.

Comment 4 Kedar Bidarkar 2015-02-24 10:35:19 UTC
Also while selecting boot-mode as static, make sure subnet also be configured with
a) nameserver 
b) gateway.

Comment 5 Marek Hulan 2015-02-24 11:31:22 UTC
I think b) DHCP as default boot-mode is right solution, so I'll implement this. As said on IRC, nameserver and gateway can't be required for subnet just because it has static boot mode. It's only relevant if you want to use the subnet for provisioning, you are using DNS etc. The only thing I can imagine to change is a note to boot mode field stating "If you select static boot mode and plan to use this subnet for provisioning you might need to specify a gateway and nameserver". But I'd prefer this in documentation rather than in form as it's already too long.

Comment 6 Marek Hulan 2015-02-25 12:46:09 UTC
Created redmine issue http://projects.theforeman.org/issues/9547 from this bug

Comment 7 Bryan Kearney 2015-03-02 11:05:11 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9547 has been closed
-------------
Marek Hulán
Applied in changeset commit:9e5fad812a64055272b9cc650c2d387027638c71.

Comment 10 Bryan Kearney 2015-03-03 15:05:34 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9547 has been closed
-------------
Marek Hulán
Applied in changeset commit:9e5fad812a64055272b9cc650c2d387027638c71.

Comment 13 Kedar Bidarkar 2015-03-13 16:23:08 UTC
As per the comment 3 and comment 5 in this bug, the default boot-mode for the UI is "DHCP".

VERIFIED with sat6.1 Beta snap6 compose2.

Comment 14 Bryan Kearney 2015-08-11 13:34:11 UTC
This bug is slated to be released with Satellite 6.1.

Comment 15 errata-xmlrpc 2015-08-12 05:25:18 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.

https://access.redhat.com/errata/RHSA-2015:1592