This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2256105 - Updating setting host_owner fails with "Value Host owner is invalid"
Summary: Updating setting host_owner fails with "Value Host owner is invalid"
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.15.0
Hardware: x86_64
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: amolpati
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-28 16:17 UTC by Gaurav Talreja
Modified: 2024-06-06 16:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:40:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37015 0 Normal Closed Updating setting host_owner fails with "Value Host owner is invalid" 2024-01-30 11:13:33 UTC
Github theforeman foreman pull 9971 0 None Merged Fixes #37015 - add validation error message for host_owner setting 2024-01-30 11:13:39 UTC
Red Hat Issue Tracker   SAT-22172 0 None Migrated None 2024-06-06 16:40:13 UTC

Description Gaurav Talreja 2023-12-28 16:17:04 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.15.0 Snap 3.0

How reproducible:
Always

Steps to Reproduce:
1. # hammer settings set --id host_owner --value 'admin'
Could not update the setting:
  Value Host owner is invalid

2. # curl -X PUT -k -H 'Content-Type: application/json' -H 'Authorization: Basic <token>=' -i 'https://satellite.example.com/api/v2/settings/host_owner' --data '{"value": "admin"}'

Actual results:
Updating setting host_owner fails with "Value Host owner is invalid"

Expected results:
Updating setting host_owner works for admin user or any created user

Additional info:
Comment 1 nalfassi 2024-01-01 13:54:00 UTC 
Created redmine issue https://projects.theforeman.org/issues/37015 from this bug
Comment 2 nalfassi 2024-01-01 15:00:05 UTC 
The provided requests are unsuccessful due to an incorrect value format. The expected format is 'ID-Users/Usergroups'.
An error message has been added to guide users on the correct input format.
Comment 4 Bryan Kearney 2024-01-30 12:02:56 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37015 has been resolved.
Comment 5 amolpati 2024-05-31 18:37:27 UTC 
Verified.

Tested on: Satellite stream snap 60

Steps followed:

1. # hammer user list     (By executing this command, you can retrieve the user ID. For example, if the ID is 1, use that ID in the command below.)

2. # hammer settings set --id host_owner --value '1-Users'     

3. After running the above command, you will receive the output - "Setting [host_owner] updated to [1-Users]"

4. To verify the second command, first run the following command which provides the token:
   # echo -n 'username:password' | base64
   
5. # curl -X PUT -k -H 'Content-Type: application/json' -H 'Authorization: Basic <token>=' -i 'https://satellite.example.com/api/v2/settings/host_owner' --data '{"value": "1-Users"}'

Both commands work properly and update the setting.
Comment 6 Eric Helms 2024-06-06 16:40:14 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.
Note You need to log in before you can comment on or make changes to this bug.