Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2223465

Summary: Registering host to Satellite using non-admin user fails in first attempt and successful after that using same command.
Product: Red Hat Satellite Reporter: Akshay Kapse <akapse>
Component: RegistrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.14.0CC: ahumbe, lstejska, nalfassi, rlavi
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, 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: 2024-06-06 16:24:49 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 Akshay Kapse 2023-07-18 02:00:37 UTC
Description of problem:
- Registration using non-admin user fails to register host with below error:
~~~
Host was not found by the subscription UUID: '', this can happen if the host is registered already, but not to this instance
~~~
- But, it is again successful if I rerun same command but assigns Default Location in place of any other defined location.

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

How reproducible:
100%

Steps to Reproduce:
1. Create a non-admin user and assign all roles.
2. Generate a registration curl command and register host.

Actual results:
- Host fails to register in first attempt.

Expected results:
- Should be able to register.

Comment 2 Leos Stejskal 2023-07-18 11:29:48 UTC
Hi,
I see that you have "ignore subman errors" set to true. Why?

> Unit d48923ce-5f36-4615-a317-6397952142d5 has been deleted (HTTP error code 410: Gone)

The message is saying that the system is already registered in the Satellite.
Please remove all the hosts from Satellite and try to register (new fresh) system again.

Comment 4 Leos Stejskal 2023-08-01 06:00:01 UTC
Hi,
what roles and permissions does the user have? I tried it with the "Register hosts" role and it works fine

Comment 12 Leos Stejskal 2023-08-02 09:04:00 UTC
> This do not show same error with same set of commands.

Yes that is expected, there were some changes and fixes in the registration process between 6.12 and 6.14.

Comment 13 Eric Helms 2024-06-06 16:24:49 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.