| Summary: | content host details page hidden for hypervisors | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Tom McKay <tomckay> | ||||
| Component: | Content Management | Assignee: | Tom McKay <tomckay> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.2.0 | CC: | cwelton, sghai, tomckay | ||||
| Target Milestone: | Unspecified | ||||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/14293 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rubygem-katello-3.0.0.31-1,rubygem-katello-3.0.0.31-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-27 11:21:13 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Tom McKay
2016-03-21 14:37:23 UTC
Created from redmine issue http://projects.theforeman.org/issues/14293 Upstream bug assigned to tomckay 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). Moving to POST since upstream bug http://projects.theforeman.org/issues/14293 has been closed ------------- Thomas McKay Applied in changeset commit:katello|bfa8bfd04ced30fec68042fcd67666cfa9263dd1. 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. Created attachment 1173733 [details]
I can see content-host details page for regsitered hypervisor
Hey Tom, Could you please take a look and comment6 and 7 and confirm that's what we should see now after fix. thanks Confirmed, marking as VERIFIED. 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 |