Red Hat Bugzilla – Bug 1194221
UI should set boot-modes appropriately under subnet
Last modified: 2017-02-23 15:28:34 EST
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.
tested, it works if dns nameserver and gateway is specified
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.
Also while selecting boot-mode as static, make sure subnet also be configured with a) nameserver b) gateway.
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.
Created redmine issue http://projects.theforeman.org/issues/9547 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/9547 has been closed ------------- Marek Hulán Applied in changeset commit:9e5fad812a64055272b9cc650c2d387027638c71.
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.
This bug is slated to be released with Satellite 6.1.
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