Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1156488 - [RFE] Re-registered hosts only show up in Content Hosts, not in Host or All Hosts
[RFE] Re-registered hosts only show up in Content Hosts, not in Host or All H...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hosts (Show other bugs)
6.0.5
Unspecified Unspecified
medium Severity medium (vote)
: Beta
: Unused
Assigned To: Justin Sherrill
Stephen Benjamin
http://projects.theforeman.org/issues...
: FutureFeature, Triaged
: 1156691 1168854 (view as bug list)
Depends On:
Blocks: 1154684
  Show dependency treegraph
 
Reported: 2014-10-24 10:51 EDT by Thom Carlin
Modified: 2016-07-27 04:45 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 04:45:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1228983 None None None Never
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 08:24:38 EDT

  None (edit)
Description Thom Carlin 2014-10-24 10:51:27 EDT
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
Comment 1 RHEL Product and Program Management 2014-10-24 10:53:26 EDT
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.
Comment 5 Dominic Cleal 2014-10-29 06:33:14 EDT
*** Bug 1156691 has been marked as a duplicate of this bug. ***
Comment 7 Xixi 2014-10-29 19:05:17 EDT
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.
Comment 8 Dominic Cleal 2014-10-30 12:43:32 EDT
Connecting redmine issue http://projects.theforeman.org/issues/3506 from this bug
Comment 9 Dominic Cleal 2014-10-30 12:49:36 EDT
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.)
Comment 10 Bryan Kearney 2014-10-30 14:05:37 EDT
Upstream bug assigned to lzap@redhat.com
Comment 13 Dominic Cleal 2014-11-28 05:11:39 EST
*** Bug 1168854 has been marked as a duplicate of this bug. ***
Comment 14 Bryan Kearney 2015-08-25 14:32:23 EDT
Upstream bug component is Hosts
Comment 16 Justin Sherrill 2016-02-26 08:15:15 EST
This provided via the host unification feature.  Moving to POST
Comment 18 Stephen Benjamin 2016-03-24 15:16:27 EDT
Verified.

A host registered only through subscription-manager now shows up under 'All Hosts' as well.
Comment 21 errata-xmlrpc 2016-07-27 04:45:52 EDT
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

Note You need to log in before you can comment on or make changes to this bug.