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:
A had a host IBM_A with a hostgroup CENTOS. This hostgroup had its location set to "Default Location". When I wanted to edit the hostgroup and change the location, it wasn't possible - it was locked because there was a host that had the hostgroup assigned.
This makes sense, so far so good.
However, in the database, the hostgroup had no location set.
When I edited the IBM_A host and unset the hostgroup, the hostgroup's location got unlocked and unset. It was not "Default Location" anymore.
Is this correct? How is it possible, that the hostgroup didn't have a location set in the DB while showing something completely different to the user in UI?
We run into this problem during CFME/Sat6 integration testing. We cannot provision into a hostgroup with no location but at the same time it all looks fine in the UI which makes it that much worse...a
Version-Release number of selected component (if applicable):
6.0.8
How reproducible:
-
Steps to Reproduce:
-
Actual results:
Discrepancy between UI and DB info.
Expected results:
Both UI and DB should give us the same data.
Additional info:
-
Comment 1RHEL Program Management
2015-06-04 18:22:29 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Ok so... to reproduce:
1. Have a host with no hostgroup but some location set
2. Have a hostgroup with no location set
3. Assign the hostgroup to the host
4. Access the hostgroup's "Locations" tab
Now it seems the hostgroup already has a location active which is not true.
The hostgroup still has no location.
The location is assigned only after you click submit, even though it looks like its already assigned.
Comment 8Daniel Lobato Garcia
2016-12-27 10:01:56 UTC
I was able to reproduce on 6.3 - once the location is blocked because the hostgroup is a assigned to a host with that location, it's impossible to assign it to the hostgroup (unless you 'unassign' from host, then assign it to the hostgroup first then to the host again).
I'll check exactly how can we solve the issue.
Comment 9Daniel Lobato Garcia
2016-12-27 10:38:10 UTC
This would easily get solved by calling `hostgroup.taxonomies.import_missing_ids` on any host - hostgroup change. It's effectively fixing mismatches, which is what we do already when we 'bulk' assign taxonomies to hosts.
Comment 10Daniel Lobato Garcia
2017-02-21 12:05:54 UTC
*** Bug 1406433 has been marked as a duplicate of this bug. ***
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.