Bug 1901716 - Cannot change Organization\Location of existing host using redhat.satellite.host module
Summary: Cannot change Organization\Location of existing host using redhat.satellite.h...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: 6.9.0
Assignee: Evgeni Golov
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-25 20:43 UTC by Sayan Das
Modified: 2024-03-25 17:14 UTC (History)
3 users (show)

Fixed In Version: ansible-collection-redhat-satellite-2.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:24:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman-ansible-modules pull 1092 0 None closed don't scope create/update requests by Organization/Location 2021-02-15 20:30:19 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:24:44 UTC

Description Sayan Das 2020-11-25 20:43:42 UTC
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 .

Comment 1 Patrick Creech 2021-01-12 21:04:53 UTC
Evgeni, is there a release of foreman-ansible-modules with this in it?

Comment 2 Evgeni Golov 2021-01-13 09:57:34 UTC
Not yet, no. But I can work on getting one for ya :)

Comment 3 Peter Ondrejka 2021-03-09 10:26:27 UTC
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

Comment 6 errata-xmlrpc 2021-04-21 13:24:18 UTC
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


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