Bug #13004
closed
Compute Profiles not Inheriting from nested host group
Description
I am running Foreman 1.10 and provisioning new hosts to VMware using template based provisioning. It appears that the configurations of my Compute Profiles are not being inherited to the Virtual Machine tab when building a new host. My host group has a default Compute profile assigned to it. It seems if I uninherit the compute profile and remove it then reselect it everything is inherited fine. I've attached a short 1minute video of my build process showing exactly what I am doing.
Files
Updated by Dominic Cleal almost 9 years ago
- Translation missing: en.field_release set to 104
Thanks for the video, that's excellent.
Updated by Dominic Cleal almost 9 years ago
- Related to Bug #12461: Compute profiles are not applied when inherited added
Updated by Dominic Cleal almost 9 years ago
- Has duplicate Bug #13145: compute profile not applied when interited from host group added
Updated by Dominic Cleal almost 9 years ago
I'm unable to reproduce this on either develop or 1.10 at the moment. Could you attach the production.log output during the selection of the host group, and also when selecting the compute resource immediately after (steps at 0:13, 0:18 of the video) please?
Updated by Chris Pisano almost 9 years ago
- File computeresource debug.txt computeresource debug.txt added
- File hostgroup debug.txt hostgroup debug.txt added
Dominic Cleal wrote:
I'm unable to reproduce this on either develop or 1.10 at the moment. Could you attach the production.log output during the selection of the host group, and also when selecting the compute resource immediately after (steps at 0:13, 0:18 of the video) please?
Attached are debug logs immediately after selecting a host group and immediately after selecting the compute resource. I think some unrelated logs might have slipped in while the compute resource was being resolved. . . my apologies for that. Please let me know if you need anything else. I just did some tests and it does seem that this is only an issue when inheriting a compute profile from a host group.
Updated by Dominic Cleal almost 9 years ago
- Subject changed from Compute Profiles not Inheriting to Compute Profiles not Inheriting from nested host group
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
Thanks for the extra data, that was helpful. I think I see when it happens now - when a profile is inherited from a parent/nested host group, it doesn't resolve. If your profile was set on the child group (rather than "Inherit parent") then it would probably work.
Updated by Chris Pisano almost 9 years ago
Dominic Cleal wrote:
Thanks for the extra data, that was helpful. I think I see when it happens now - when a profile is inherited from a parent/nested host group, it doesn't resolve. If your profile was set on the child group (rather than "Inherit parent") then it would probably work.
You are correct. I created a parent group with no compute profile set and a nested group with a compute profile set. Everything is inherited without issue.
Updated by The Foreman Bot almost 9 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3071 added
Updated by Dominic Cleal almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 05d9c49e6662e1fceae03ff8a9a739ec6991c691.