Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Given a host that is using a different CV/LE than its hostgroup. When editing it, the hostgroups's default CV and LE are loaded. This behaviour is quite confusing as it makes people think that the updating is not successful after clicking on the submit button.
Version-Release number of selected component (if applicable):
6.3.1
How reproducible:
Easy
Steps to Reproduce:
1. Create a hostgroup with a CV and LE
2. Create a host with the hostgroup
3. Edit the host with a different CV and LE
4. Check the editing host page again
Actual results:
On the editing host page, it shows the hostgroups's default CV and LE.
Expected results:
It should show the CV and LE that match the db entry.
Andrew, could this be a duplicate of bug 1566825 that you are investigating.
I saw Samir's comment on the card:
In 6.2 editing host env, cv triggers task Actions::Katello::Host::Update However, in 6.3 this task is not triggered.
If that is the case, it may be the same cause.
I don't think it's related because the host record and content facet are properly updated in 1566825, but the Actions::Katello::Host::Update task (which updates backend services) isn't run, which causes `subscription-manager identity` on the host to give the old information.