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:
Although virt-who has send host/guest association to satellite server, it can't show on the satellite web UI.
Version-Release number of selected component (if applicable):
candlepin-0.9.43-1.el7.noarch.rpm
foreman-1.7.2.6-1.el7sat.noarch.rpm
katello-2.2.0.5-1.el7sat.noarch.rpm
How reproducible:
Always
Steps to Reproduce:
1. Register rhel7.1 host and guest to satellite server
[root@hp-z220-05 ~]# subscription-manager register --username=admin --password=admin
The system has been registered with ID: b8fe5576-6b97-48fc-ad85-753f3bcc614d
2. Restart virt-who service
# systemctl restart virt-who
3. Make sure virt-who has send host/guest associate to satellite server
2015-02-27 17:26:42,720 [INFO] @libvirtd.py:186 - Using libvirt url: ""
2015-02-27 17:26:42,729 [DEBUG] @libvirtd.py:215 - Virtual machine found: 7.0_Server_x86_64: 0830b3b4-2e45-4c2e-8420-818c00d7e743
2015-02-27 17:26:42,730 [DEBUG] @libvirtd.py:221 - Virtual machine found: 6.5_Client_i386: 148d8fc0-6637-4cdc-a470-0ced83aa0307
2015-02-27 17:26:42,730 [DEBUG] @libvirtd.py:221 - Virtual machine found: 6.4_Server_x86_64: 6f04a680-1691-4362-8987-c1c2cee58afa
2015-02-27 17:26:42,731 [DEBUG] @libvirtd.py:221 - Virtual machine found: 5.10_Server_x86_64: 04f5d08b-7a07-455e-9da4-54715a4c6815
2015-02-27 17:26:42,931 [INFO] @subscriptionmanager.py:110 - Sending list of uuids: ['04f5d08b-7a07-455e-9da4-54715a4c6815', '0830b3b4-2e45-4c2e-8420-818c00d7e743', '148d8fc0-6637-4cdc-a470-0ced83aa0307', '6f04a680-1691-4362-8987-c1c2cee58afa']
4. Open satellite web UI, check Host--> Content host --> [host name] --> Detail -->Basic Information
or Open satellite web UI, check Host--> Content host --> [guest name] --> Detail -->Basic Information
Actual results:
It can't show host's guest info under the host's detail page.
It also can't show guest's host info under the host's detail page. please see screenshot on attachment.
Expected results:
It should show the correct host/gues info in their detail info, like Satellite-6.0.4-RHEL-7-20150216.0. please see the correct screenshot on attachment.
On the guest as the following: "Virtual Host hp-z220 05.qe.lab.eng.nay.redhat.com"
On the host as the following: "Virtual Guests 1 Content Host"
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9646 has been closed
-------------
Thomas McKay
Applied in changeset commit:katello|4bc5956eeba875bd51fdf49f0eba25d2ae382440.
Do the same test as bug description on the latest Satellite610, the host/guest type is show on the webUI now.Therefore, Verify it on Satellite-6.1.0-RHEL-7-20150310.0.
Verified Version:
katello-2.2.0.7-1.el7sat.noarch
candlepin-0.9.43-1.el7.noarch
foreman-1.7.2.9-1.el7sat.noarch
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-2015:1592