Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1810825 - custom operating system unable to be set at registration time [NEEDINFO]
Summary: custom operating system unable to be set at registration time
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: tstrych
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-06 00:03 UTC by Paul Dudley
Modified: 2021-05-20 09:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
oezr: needinfo? (pdudley)

Attachments (Terms of Use)

Description Paul Dudley 2020-03-06 00:03:58 UTC
Description of problem:
After registering a host with the bootstrap.py script a custom operating system is not set after specifying a hostgroup that includes the custom OS and the -O parameter (to specify operating system) once more. The custom OS is also not set when using just the hostgroup.

How reproducible:
Satellite 6.6 100% reproducible on test satellite/client

Steps to Reproduce:
1. create custom OS, assign proper parameters and arch
2. assign OS to hostgroup
3. use bootstrap.py to register the host

Actual results:
The custom OS is not assigned in the Satellite webui to the host

Expected results:
The custom OS should be assigned

Additional Info:
Looking at logs we can see the right parameter being passed:
Parameters: {"host"=>{"operatingsystem_id"=>9,

But still the POST is:
2020-02-28T17:25:28 [I|aud|6a929fae] Host::Base (904) update event on operatingsystem_id 9, 3

In the above, OS 9 is the custom OS and 3 is the true OS of the system. 3 would be the correct OS to assign if we were not passing custom parameters.

Note You need to log in before you can comment on or make changes to this bug.