Description of problem: Host group information does not populate on the edit screen of a discovered host when clicking the customize host button. The Organization, Location, and Host group are all populated on the edit screen. The Lifecycle Environment, Content View, partition table and more are empty. Version-Release number of selected component (if applicable): Satellite 6.10.2 How reproducible: Every time Steps to Reproduce: 1. Discover a host 2. From the discovered host screen, click "Provision" to the right of the discovered host. 3. Select the Host group, Organization, and Location in the popup, then click "Customize Host" Actual results: Edit page for the host renders with all information from the host group not populated. Expected results: All fields are populated with selected host group information. Additional info: WORKAROUND: - Clear the host group field on the edit page - Select the same host group from the host group dropdown list Information will populate in the fields based on the host group configuration.
From my testing it seems like this might be related https://bugzilla.redhat.com/show_bug.cgi?id=1955046. I've also noticed that host group clones aren't actually copying over all of the information. I'm not entirely sure this is a Discovery Image issue, but more of a Host Group / Provisioning issue.
(In reply to Griffin Sullivan from comment #2) > From my testing it seems like this might be related > https://bugzilla.redhat.com/show_bug.cgi?id=1955046. I've also noticed that > host group clones aren't actually copying over all of the information. I'm > not entirely sure this is a Discovery Image issue, but more of a Host Group > / Provisioning issue. In our testing for the customer we found the issue was related to provisioning (host creation) in general, and not specific to discovered hosts or the discovery plugin, so I believe this is right and they could be related. The customer here confirms the same issues with synced media dissociating, but also sees base attributes like LCE and CV failing to stay auto-populated
Thanks for getting back to us, resetting the component.
Closing as dupe of 2069324 after discussing with Taft that they are likely the same issue *** This bug has been marked as a duplicate of bug 2069324 ***