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.

Created attachment 1053194 [details]
screenshot

Description of problem:
In the WebUI when using the "Unregister Content Hosts" command as a Bulk Action errored but completes the action

Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 13

How reproducible:
Always

Steps to Reproduce:
1. Go to Hosts -> Content Hosts -> Select 3+ content hosts -> Bulk Actions -> Unregister Content host


Actual results:
I get the following error message in UI but the content hosts are gone from UI:
"At least one content host needs to be selected in order to perform a bulk action."

But the content hosts are unregistered:

# subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Unknown

Expected results:
No error in UI

Additional info:

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.

Please see related bugs

https://bugzilla.redhat.com/show_bug.cgi?id=1338578
https://bugzilla.redhat.com/show_bug.cgi?id=1209866
https://bugzilla.redhat.com/show_bug.cgi?id=1244309
https://bugzilla.redhat.com/show_bug.cgi?id=1276241
https://bugzilla.redhat.com/show_bug.cgi?id=1325879
https://bugzilla.redhat.com/show_bug.cgi?id=1212674

Please see related bugs

https://bugzilla.redhat.com/show_bug.cgi?id=1338578
https://bugzilla.redhat.com/show_bug.cgi?id=1209866
https://bugzilla.redhat.com/show_bug.cgi?id=1244309
https://bugzilla.redhat.com/show_bug.cgi?id=1276241
https://bugzilla.redhat.com/show_bug.cgi?id=1325879
https://bugzilla.redhat.com/show_bug.cgi?id=1212674

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

I am not able to reproduce this on 6.2 and as it has been moved to a background task i bet it has changed quite a bit from 6.1