Bug #11022
closed
Using a hostgroup with realm makes realm sticky
Added by Jon Skarpeteig about 9 years ago.
Updated about 9 years ago.
Description
Using a hostgroup that has realm set, removing realm from new host creation (selecting blank) - still use old value.
- Related to Bug #9591: Override puppet configuration on host level does not work if specified on host group added
- Category set to Host creation
- Translation missing: en.field_release deleted (
62)
Same sort of issue that #9591 may solve once complete. By the way, please only set the "Found in release" field, not "Release" (as that's for when it's shipped).
Seems to be related, but it's a bit more complex:
Creating a new host (without hostgroup), leaving the realm field blank - great success
Editing the host adding it to a host group (while realm is still blank) - Fail: it tries to write realm
Also; seems there's no realm dropdown in the hostgroups UI at all, so not sure where it comes from to begin with
Jon Skarpeteig wrote:
Also; seems there's no realm dropdown in the hostgroups UI at all, so not sure where it comes from to begin with
It should be under the Network tab of the host group form.
Ah, right. Another bug then. Realm not updated in UI when selecting hostgroup.
- Status changed from New to Resolved
Thanks for the report, I believe this is now fixed for Foreman 1.10 via #9591.
Also available in: Atom
PDF
Updated by 
Updated by