Bug 1878693

Description of problem:

Unable to check the information about resource "images" or build a host by spcifying "image" keyword with "hosts" module from Satellite Ansible collections.


Version-Release number of selected component (if applicable):
Red Hat Satellite 6.7

How reproducible:
Always

Steps to Reproduce:
1. Create a basic satellite setup with HG\CR\CP\DHCP\TFTP\DNS etc configured.
2. Create a image in satellite UI inside the compute resource using the existing templates in your Vmware infra.
3. Create a ansible playbook using Satellite Ansible collections as displayed below to either check the information about "images" or perform a "image" based deployment and execute the same.
~~~
    - name: Get image resources
      redhat.satellite.resource_info:
        username: "{{ satellite_username }}"
        password: "{{ satellite_password }}"
        server_url: "{{ satellite_url }}"
        organization: "{{ satellite_organization }}"
        resource: images
      register: images
      ignore_errors: true

    - debug: var=images


    - name: Create a host
      redhat.satellite.host:
        username: "{{ satellite_username }}"
        password: "{{ satellite_password }}"
        server_url: "{{ satellite_url }}"
        organization: "{{ satellite_organization }}"
        name: "testhost.example.com"
        location: "GSS"
        hostgroup: "satellite_image"
        build: true
        compute_profile: "Vmware-Satellite"
        compute_resource: "optimus"
        provision_method: "image"
        image: "RHEL7.8"
        state: present
      register: build


    - debug: var=build  
~~~

Actual results:
~~
$ ansible-playbook test.yaml -k --vault-password-file .vault 
SSH password: 
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details

PLAY [Test hosts modules for image based build] *****************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************************
ok: [satellite.example.com]

TASK [Set few facts.] *******************************************************************************************************************************************************************
ok: [satellite.example.com]

TASK [Get image resources] **************************************************************************************************************************************************************
fatal: [satellite.example.com]: FAILED! => changed=false 
  msg: 'Failed to list resource: "missing param ''operatingsystem_id'' in parameters"'
...ignoring

TASK [debug] ****************************************************************************************************************************************************************************
ok: [satellite.example.com] => 
  images:
    changed: false
    failed: true
    msg: 'Failed to list resource: "missing param ''operatingsystem_id'' in parameters"'

TASK [Create a host] ********************************************************************************************************************************************************************
fatal: [satellite.example.com]: FAILED! => changed=false 
  msg: 'Failed to list resource: "missing param ''operatingsystem_id'' in parameters"'

PLAY RECAP ******************************************************************************************************************************************************************************
satellite.example.com : ok=4    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=1   
~~

Expected results:

The module should be able to find the image by looking inside associated compute resource and then the host build should be submitted successfully.


Additional info:

* From my prospective in both of the scenarios, It seems when the host modules tries to look for the image resource, It's not looking for the same inside "compute resource". 

* To demonstrate further via hammer,

hammer> compute-resource image list --compute-resource optimus
---|---------|------------------|----------|--------------------------------------|----------
ID | NAME    | OPERATING SYSTEM | USERNAME | UUID                                 | USER DATA
---|---------|------------------|----------|--------------------------------------|----------
1  | RHEL7.8 | RHEL Server 7.8  | root     | 50001356-2221-54b5-a3af-94dadaad981b | false    
---|---------|------------------|----------|--------------------------------------|----------

hammer> compute-resource image info --name "RHEL7.8"
missing param 'operatingsystem_id' in parameters


hammer> compute-resource image info --name "RHEL7.8" --compute-resource optimus
Id:               1
Name:             RHEL7.8
Operating System: RHEL Server 7.8
Username:         root
UUID:             50001356-2221-54b5-a3af-94dadaad981b
User Data:        false
Architecture:     x86_64
Created at:       2020/06/23 16:22:34



Updated at:       2020/08/25 05:49:48