Bug 1107703
| Summary: | After registering content host, it is not listed | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Adam Saleh <asaleh> |
| Component: | Subscription Management | Assignee: | Eric Helms <ehelms> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.3 | CC: | bbuckingham, cwelton, jmontleo, tkolhar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/6171 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-02 14:09:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Adam Saleh
2014-06-10 12:54:00 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. 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. 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. Created redmine issue http://projects.theforeman.org/issues/6171 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/6171 has been closed 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 This was delivered in 6.0.3, the Beta version of Satellite 6.0 This was delivered with 6.0.3, which is the Satellite 6 Beta. |