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.
Bug 1319797 - content host details page hidden for hypervisors
Summary: content host details page hidden for hypervisors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 14:37 UTC by Tom McKay
Modified: 2019-09-26 17:35 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-3.0.0.31-1,rubygem-katello-3.0.0.31-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:21:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
I can see content-host details page for regsitered hypervisor (61.74 KB, image/png)
2016-06-29 09:55 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14293 0 None None None 2016-04-22 15:51:25 UTC

Description Tom McKay 2016-03-21 14:37:23 UTC 
A pure hypervisor (as created via virt-who) has its content host details page hidden with message
<pre>
This Host is not currently registered with subscription-manager. Click here for registration information.
</pre>

The hiding should only happen only if there is neither host.hasContent() nor host.hasSubscription() is true.
Comment 1 Tom McKay 2016-03-21 14:37:25 UTC 
Created from redmine issue http://projects.theforeman.org/issues/14293
Comment 2 Tom McKay 2016-03-21 14:37:29 UTC 
Upstream bug assigned to tomckay
Comment 4 Tom McKay 2016-03-21 18:00:28 UTC 
To verify fix:
Register a hypervisor and visit the content host details page. Previously it would indicate that the host had not been registered. Now it should show subscription basic details (name, sub status).
Comment 5 Bryan Kearney 2016-03-28 20:03:16 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14293 has been closed
-------------
Thomas McKay
Applied in changeset commit:katello|bfa8bfd04ced30fec68042fcd67666cfa9263dd1.
Comment 6 Sachin Ghai 2016-06-29 09:54:15 UTC 
Verified with sat62 GA snap17

I can see content-host details page for registered hypervisor. I can see name and status. Please see attached screenshot.
Comment 7 Sachin Ghai 2016-06-29 09:55:01 UTC 
Created attachment 1173733 [details]
I can see content-host details page for regsitered hypervisor
Comment 8 Sachin Ghai 2016-06-29 09:56:09 UTC 
Hey Tom, Could you please take a look and comment6 and 7 and confirm that's what we should see now after fix. thanks
Comment 9 Tom McKay 2016-06-30 13:34:58 UTC 
Confirmed, marking as VERIFIED.
Comment 10 Bryan Kearney 2016-07-27 11:21:13 UTC 
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/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.