Bug 1573629
| Summary: | Unclear Error when performing bulk action of Manage Repository Set against Hosts without Content registration | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Dylan Gross <dgross> | ||||
| Component: | Hosts - Content | Assignee: | Samir Jha <sajha> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3.1 | CC: | ktordeur, sajha, sghai, zhunting | ||||
| Target Milestone: | 6.4.0 | Keywords: | EasyFix, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-10-16 19:31:36 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: | |||||||
| Attachments: |
|
||||||
|
Description
Dylan Gross
2018-05-01 19:53:20 UTC
Created redmine issue http://projects.theforeman.org/issues/23887 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23887 has been resolved. Created attachment 1482126 [details]
Verified - Mange repository set success
Verified!
@ Satellite 6.4 snap 20
Steps:
1. Created a Host which is not registered and not checked in.
2. From WebUI -> Content Hosts and selected a number of hosts, including the one just created (which should show as "Never registered" and "Never checked in"
3. Selected "Select Action" -> "Manage Repository Sets" and choose a Repository set and either "Override to Enabled".
Observation:
The task did not fail, and just posted a warning, with an explanation of the failure.
Verification screenshot attached.
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/RHSA-2018:2927 |