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.
DescriptionWaldirio M Pinheiro
2018-11-20 19:24:11 UTC
Description of problem:
On the CP database we are able to see the correct information from hypervisors versus guests from the virtualization environment but on the Satellite webUI the information is incorrect and as consequence, the customer is not able to move forward assigning the correct entitlement (virtual).
Version-Release number of selected component (if applicable):
6.3.5
How reproducible:
100% in the customer environment
Steps to Reproduce:
1. Run virt-who
2. See all process conclude with successful
3. On the Satellite webUI the information related to the Guests on the hypervisor (virt-who-<fqdn>) still out of date.
Actual results:
Incorrect information.
Expected results:
See the correct information related to Guests/Content Hosts running on top of that hypervisor.
Additional info:
Verified in Satellite 6.5.0 Snap 11
Steps:
clone https://github.com/JacobCallahan/content-host-d
inside that directory build the guest image
docker build -t ch-d:guest RHEL7-Guest/.
install docker-py
run the flood script with the following arguments
python flood.py -s ibm-x3550m3-07.lab.eng.brq.redhat.com --hypervisors 2 --guests 5 --tag guest
The script will handle everything for you but will give you a chance to attach subscriptions to your hypervisors.
All hypervisor-guest mappings are working correctly
See attached screenshots for verification.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222
** Satellite 6.4.3 Hotfix **
This fix includes a fix for this bug as well as the hotfix previously released in:
https://bugzilla.redhat.com/show_bug.cgi?id=1687378#c31
1) download HF-1687378-1651774-6.4.3.tar from bugzilla to Satellite 6.4.2 server
2) unpack and install:
rpm -Uvh tfm-rubygem-katello-3.7.0.56-5.HOTFIXRHBZ1687378_1651774.el7sat.noarch.rpm tfm-rubygem-katello-3.7.0.56-5.HOTFIXRHBZ1687378_1651774.el7sat.noarch.rpm
3) restart services
foreman-maintain service restart
4) resume operations