Bug #36980
closedReassigning a new hostgroup to an existing host does not update the Lifecycle environment and content view for the host.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2253496
Description of problem:
Reassigning a new HostGroup to an existing host does not update the Lifecycle environment and content view in the Hostprofile.
Version-Release number of selected component (if applicable):
6.14
How reproducible:
100%
Steps to Reproduce:
1. Create two HostGroups ( A & B) in the satellite.
2. Deploy a host using HostGroup A.
3. Next navigate to Hosts > All Hosts > select the Host > Select action drop-down menu > Change Group > Assign B HostGroup > Submit
4. Edit the host profile, the HostGroup B is assigned to the host.
Actual results:
However, the Lifecycle env and content view is not updated with the Lifecycle env and content view assigned to the new HostGroup.
Expected results:
With the assignment of a new HostGroup, the HostGroup attributes should be updated on the client by default. Ex. Lifecycle env and content view
Additional info:
In 6.13, we have the option and we can edit the Host and update the Lifecycle env and content view however post upgrade to 6.14 these options are graded out.
Updated by The Foreman Bot 10 months ago
- Status changed from New to Ready For Testing
- Assignee set to Lucy Fu
- Pull request https://github.com/theforeman/foreman/pull/9953 added
Updated by The Foreman Bot 9 months ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/9953)
Updated by Lucy Fu 9 months ago
- Project changed from Foreman to Katello
- Subject changed from Reassigning a new hostgroup to an existing host does not update the Lifecycle environment and content view for the host. to Reassigning a new hostgroup to an existing host does not update the Lifecycle environment and content view for the host.
- Category deleted (
Host groups)
Updated by Quinn James 9 months ago
- Category set to Hosts
- Status changed from Assigned to Duplicate
This bug conflicts with the functionality of #36897; we've decided to go ahead with fixing the other bug instead. Hosts should maintain their lifecycle environment and content view settings irrespective of changes to the host group.