Project

General

Profile

Actions

Bug #11022

closed

Using a hostgroup with realm makes realm sticky

Added by Jon Skarpeteig almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Using a hostgroup that has realm set, removing realm from new host creation (selecting blank) - still use old value.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #9591: Override puppet configuration on host level does not work if specified on host groupClosedShimon Shtein03/01/2015Actions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #9591: Override puppet configuration on host level does not work if specified on host group added
Actions #2

Updated by Dominic Cleal almost 9 years ago

  • 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).

Actions #3

Updated by Jon Skarpeteig almost 9 years ago

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

Actions #4

Updated by Jon Skarpeteig almost 9 years ago

Also; seems there's no realm dropdown in the hostgroups UI at all, so not sure where it comes from to begin with

Actions #5

Updated by Dominic Cleal almost 9 years ago

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.

Actions #6

Updated by Jon Skarpeteig almost 9 years ago

Ah, right. Another bug then. Realm not updated in UI when selecting hostgroup.

Actions #7

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Resolved

Thanks for the report, I believe this is now fixed for Foreman 1.10 via #9591.

Actions

Also available in: Atom PDF