Description of problem: When a system is re-registered from RHN Classic to Sat6, the system only displays in "Content Hosts", not in "Host" nor "All Hosts" Version-Release number of selected component (if applicable): 6.0.5 How reproducible: Each time Steps to Reproduce: 1. Re-register system 2. webUI > Content Hosts 3. Actual results: System appears but not in "All Hosts" Expected results: System appears in all 3 places Additional info: Re-registration steps are in GSS case 1271296
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.
*** Bug 1156691 has been marked as a duplicate of this bug. ***
Adding to RFE review... There's a doc Bug 1149145 [Documentation] Need clear definition and difference of "All Hosts" and "Content Hosts" under "Hosts" tab in Red Hat Satellite v 6 webui Public summary from https://bugzilla.redhat.com/show_bug.cgi?id=1149145#c5: Per discussion with engineering, there are existing plans to improve the page so that the two lists will be merged into one with all of the hosts, to reduce confusion. In the meantime, Bug 1149145 is for clarification in the Satellite 6 documentation, with suggested verbiage from https://access.redhat.com/solutions/1228983 which explains which hosts are listed where and how to add a host from Content Hosts to the All Hosts page.
Connecting redmine issue http://projects.theforeman.org/issues/3506 from this bug
Linking a feature that was started, in which we intended to include Puppet agent configuration as part of subscription registration. (I get the impression this is less about the UI, more about the lack of client configuration.)
Upstream bug assigned to lzap
*** Bug 1168854 has been marked as a duplicate of this bug. ***
Upstream bug component is Hosts
This provided via the host unification feature. Moving to POST
Verified. A host registered only through subscription-manager now shows up under 'All Hosts' as well.
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:1500