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.

Description of problem: After registering new client to satellite in default location. it fails to assign new location to client and raise error

Unregister host vm253-211.gsslab.pnq2.redhat.com before assigning an organization

Screen attached

Version-Release number of selected component (if applicable): Satellite 6.8


How reproducible: Always


Steps to Reproduce:
1. Register host to satellite in default location
2. Try to change location using bulk action
3. It fails. check screen shot

Created attachment 1712634 [details]
Screen 1

Created attachment 1712636 [details]
Screen 2

Created attachment 1712637 [details]
Screen 3

Is this a regression from Satellite 6.7?

Thanks for raising the BZ.  The behavior described is a duplicate of bug 1868183 and has a patch upstream.

*** This bug has been marked as a duplicate of bug 1868183 ***