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 1347427 - Content host details page should be explicit about unregistered clients
Summary: Content host details page should be explicit about unregistered clients
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-16 20:14 UTC by Justin Sherrill
Modified: 2019-09-26 17:32 UTC (History)
4 users (show)

Fixed In Version: rubygem-katello-3.0.0.53-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 10:59:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
unregistered system (91.82 KB, image/png)
2016-06-17 15:51 UTC, Justin Sherrill
no flags Details
unregistered system (Post change) (20.48 KB, image/png)
2016-06-20 18:32 UTC, Justin Sherrill
no flags Details
after unregistering host, details page (20.48 KB, image/png)
2016-07-01 10:16 UTC, Sachin Ghai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15456 0 None None None 2016-06-17 19:01:33 UTC

Description Justin Sherrill 2016-06-16 20:14:33 UTC
After registering and then unregistering a client and visiting the content host page, the user sees a details page where most of the info is missing.

We should just hide all this and display a message suggesting they register it.

Comment 1 Brad Buckingham 2016-06-17 15:27:35 UTC
Hi Justin, a request from triage.  Can you provide a description of what the user sees today and how you recommend this change to improve the user behavior?

Comment 4 Justin Sherrill 2016-06-17 15:51:25 UTC
Created attachment 1169158 [details]
unregistered system

Comment 6 Justin Sherrill 2016-06-17 18:16:37 UTC
Created redmine issue http://projects.theforeman.org/issues/15456 from this bug

Comment 7 Justin Sherrill 2016-06-20 18:32:06 UTC
Created attachment 1169965 [details]
unregistered system (Post change)

Comment 8 Bryan Kearney 2016-06-20 20:16:19 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/15456 has been closed

Comment 9 Sachin Ghai 2016-07-01 10:16:15 UTC
Verified with sat62 GA snap18.1

I registered a content-host with satellite and can see all its details under content-host details. But when I unregistered it, it says:


This Host is not currently registered with subscription-manager. Click here for registration information.

Comment 10 Sachin Ghai 2016-07-01 10:16:57 UTC
Created attachment 1174873 [details]
after unregistering host, details page

Comment 11 Bryan Kearney 2016-07-27 10:59:20 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.