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 1107703 - After registering content host, it is not listed
Summary: After registering content host, it is not listed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-10 12:54 UTC by Adam Saleh
Modified: 2019-09-26 18:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 14:09:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6171 0 None None None 2016-04-22 15:00:38 UTC

Description Adam Saleh 2014-06-10 12:54:00 UTC
Description of problem:

After subscribng host to sat6 it is not shown in content host list, nor with hammer cli.

Steps to Reproduce:
1. register host by standard means i.e.: subscription-manager register --force --org="ACME_Corporation" --environment="Library"
2. observe "The system has been registered with id:$HOST-ID" message
3. try hammer content-host info --id=$HOST-ID and observe, that host was registered
4. try hammer content-host list --organization-label='ACME_Corporation'
5. try list content hosts for ACME_Corporation in ui

Actual results:
No data.

Expected results:
At least the registered host should have been listed

Comment 1 RHEL Program Management 2014-06-10 13:07:27 UTC
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 3 Eric Helms 2014-06-11 12:18:57 UTC
Pushing back to QA to re-test with the latest snap. While we were able to see this on the affected system, I was not able to reproduce this elsewhere and thus feel this is either a transient bug or one that requires a more detailed and specified scenario in order to reproduce. If this is able to be re-produced with the next snap, I would ask that the foreman-debug output and a detailed scenario be provided around what may or may not have been done prior to or at the same time as the registration.

Comment 4 Eric Helms 2014-06-11 14:22:06 UTC
After further thinking and review, I was able to reproduce this under the following scenario.

1. Put Pulp into a state that will throw an error during registration (e.g. 500, or Timeout) in our case we can force it with 'service mongod stop'
2. Register a system
3. System should fail to register with errors and not be visible in the Content Host list
4. Start mongo 'service mongod start'
5. Re-register the system
6. System will claim to register successfully but viewing the Content Host list will not show the system
7. Go to Monitor -> Tasks
8. Find the failed, original system registration
9. While viewing the details of the failed system registration, click resume
10. Visit the Content Host page when it has completed, and two entries will be present


Note that this affects all systems that try to register after the first failed one. In other words, once a system fails to register, until that task is resumed, all other systems that register will not appear in the list.

Comment 5 Eric Helms 2014-06-11 17:51:29 UTC
Created redmine issue http://projects.theforeman.org/issues/6171 from this bug

Comment 6 Bryan Kearney 2014-06-11 20:55:05 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/6171 has been closed

Comment 9 Tazim Kolhar 2014-06-17 07:22:45 UTC
VERIFIED

# hammer content-host info --id 1037ddc5-aadf-42df-98b8-3b290aac95a3
Name:                  hp-bl420cgen8-01.rhts.eng.bos.redhat.com
ID:                    1037ddc5-aadf-42df-98b8-3b290aac95a3
Description:           Initial Registration Params
Location:              None
Lifecycle Environment: Library
Content View:          Default Organization View
Entitlement Status:    invalid
Release Version:       
Autoheal:              true

# hammer content-host list --organization-label ACME_Corporation
-------------------------------------|-----------------------------------------
ID                                   | NAME                                    
-------------------------------------|-----------------------------------------
1037ddc5-aadf-42df-98b8-3b290aac95a3 | hp-bl420cgen8-01.rhts.eng.bos.redhat.com
-------------------------------------|-----------------------------------------

In UI also the registered content host is visible

Comment 10 Bryan Kearney 2014-07-02 14:09:08 UTC
This was delivered in 6.0.3, the Beta version of Satellite 6.0

Comment 11 Bryan Kearney 2014-07-02 14:09:08 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.


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