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.
Description of problem:
Right now if someone wants to update hostgroup information for an existing host, they can easily use the redhat.satellite.host module but It seems the organization and location settings for a host cannot be changed yet.
Version-Release number of selected component (if applicable):
Satellite 6.7.4
Satellite Ansible Collection
How reproducible:
Always
Steps to Reproduce:
1. Register a host "clienthost.example.com" in satellite server and ensure it's associated with following.
ORG = RedHat
Location = GSS
Hostgroup = None at this moment
2. Create a playbook to update the hostgroup information and ensure that Org and Location are set to RedHat and GSS respectively.
~~~
- name: Update a host
redhat.satellite.host:
username: "{{ satellite_username }}"
password: "{{ satellite_password }}"
server_url: "{{ satellite_url }}"
organization: "RedHat"
name: "clienthost.example.com"
location: "GSS"
hostgroup: "Parent/Child1/RHEL7"
state: present
~~~
3. Execute the playbook.
4. Now modify the playbook to point to a different location.
~~
- name: Update a host
redhat.satellite.host:
username: "{{ satellite_username }}"
password: "{{ satellite_password }}"
server_url: "{{ satellite_url }}"
organization: "RedHat"
name: "clienthost.example.com"
location: "MPS"
hostgroup: "Parent/Child1/RHEL7"
state: present
~~
5. Re-execute the playbook.
Actual results:
At step 3, The execution will be successful
At Step 5, The execution will be failed with following error.
~~
ansible_facts:
discovered_interpreter_python: /usr/bin/python
error:
message: Resource host not found by id '195'
msg: 'Error while performing update on hosts: 404 Client Error: Not Found'
~~
Expected results:
The playbook should be able to change the location as well.
Additional info:
* My observation is that the organization\location parameters are basically being used for searching the host but those are not for updating. So the 404 error is expected from that point of view , when i change the location.
* The hammer utility have some options to override the host location and organisation.
~~
hammer host update --new-location XXX --new-organization YYYY --name host.example.com
~~
--> The host module itself should also have such options using which the location and organization can be changed if user wants to .
Verified on Satellite 6.9 sn 16 using automation run (test_playbooks/host.yml "move host to second org/loc"), confirming the changes landed in ansible-collection-redhat-satellite.noarch 0:2.0.1-1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1313
Description of problem: Right now if someone wants to update hostgroup information for an existing host, they can easily use the redhat.satellite.host module but It seems the organization and location settings for a host cannot be changed yet. Version-Release number of selected component (if applicable): Satellite 6.7.4 Satellite Ansible Collection How reproducible: Always Steps to Reproduce: 1. Register a host "clienthost.example.com" in satellite server and ensure it's associated with following. ORG = RedHat Location = GSS Hostgroup = None at this moment 2. Create a playbook to update the hostgroup information and ensure that Org and Location are set to RedHat and GSS respectively. ~~~ - name: Update a host redhat.satellite.host: username: "{{ satellite_username }}" password: "{{ satellite_password }}" server_url: "{{ satellite_url }}" organization: "RedHat" name: "clienthost.example.com" location: "GSS" hostgroup: "Parent/Child1/RHEL7" state: present ~~~ 3. Execute the playbook. 4. Now modify the playbook to point to a different location. ~~ - name: Update a host redhat.satellite.host: username: "{{ satellite_username }}" password: "{{ satellite_password }}" server_url: "{{ satellite_url }}" organization: "RedHat" name: "clienthost.example.com" location: "MPS" hostgroup: "Parent/Child1/RHEL7" state: present ~~ 5. Re-execute the playbook. Actual results: At step 3, The execution will be successful At Step 5, The execution will be failed with following error. ~~ ansible_facts: discovered_interpreter_python: /usr/bin/python error: message: Resource host not found by id '195' msg: 'Error while performing update on hosts: 404 Client Error: Not Found' ~~ Expected results: The playbook should be able to change the location as well. Additional info: * My observation is that the organization\location parameters are basically being used for searching the host but those are not for updating. So the 404 error is expected from that point of view , when i change the location. * The hammer utility have some options to override the host location and organisation. ~~ hammer host update --new-location XXX --new-organization YYYY --name host.example.com ~~ --> The host module itself should also have such options using which the location and organization can be changed if user wants to .