Bug #9108: It's not possible to overwrite a default value of a parameter inherited from parent host group in nested host group - Foreman

Actions

Copy link

Bug #9108

closed

It's not possible to overwrite a default value of a parameter inherited from parent host group in nested host group

Added by Filip Brychta over 10 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Tom Caspy

Category:

Host groups

Target version:

1.9.1

Difficulty:

Triaged:

Bugzilla link:

1295179

Pull request:

https://github.com/theforeman/foreman/pull/2128

Fixed in Releases:

Found in Releases:

1.7.1

Red Hat JIRA:

Description

1 - create a new host group named 'parent' with global parameter named 'parameter1' with value 'parentValue'
2 - create a new host group named 'child' and set Parent to host group created in step 1. and change value of 'parameter1' to 'changed'

Result:
Value of 'parameter1' in 'child' host group is still 'parentValue'
Value of 'parameter1' in 'child' host group is editable but no change is applied.

Actions

Copy link

Updated by Tom Caspy over 10 years ago

this is indeed a bug.
Current workaround - the value can be overridden by adding a new global parameter with the same name, and overriding the value there.

Actions

Copy link

Updated by Filip Brychta over 10 years ago

Tom Caspy wrote:

this is indeed a bug.
Current workaround - the value can be overridden by adding a new global parameter with the same name, and overriding the value there.

Note that this workaround (duplicate parameters in the hostgroup) will lead to #8366

Actions

Copy link

Updated by Tom Caspy about 10 years ago

checked... didn't break anything... apparently the bug is that the shown parameter isn't actually something which exists in the DB, I'll investigate further as to why this happens.

Filip Brychta wrote:

Tom Caspy wrote:

this is indeed a bug.
Current workaround - the value can be overridden by adding a new global parameter with the same name, and overriding the value there.

Note that this workaround (duplicate parameters in the hostgroup) will lead to #8366