Verified on stream snap 56.0

VMWare compute profile made with Satellite Ansible Collection shows the name of the storage pod in the UI that was used in the playbook.

Steps to reproduce:

1) Make a compute resource for VMware (named 'test' in this example)

2) Run playbook for creating the compute profile:

---
- name: test compute profile
  hosts: localhost
  vars:
  - compute_profiles:
      - name: Small
        compute_attributes:
          - compute_resource: "test"
            vm_attrs:
              cluster: ClusterName
              resource_pool: Resources
              cpus: 1
              corespersocket: 1
              memory_mb: 2048
              firmware: bios
              guest_id: rhel8_64Guest
              ha: 1
              scsi_controllers:
                - type: ParaVirtualSCSIController
              volumes_attributes:
                0:
                  size_gb: 100
                  thin: false
                  mode: persistent
                  storage_pod: StoragePodName
              interfaces_attributes:
                0:
                  type: VirtualVmxnet3
                  network: VLAN111
  tasks:
    - name: Create compute profiles
      redhat.satellite.compute_profile:
        name: "{{ item.name }}"
        compute_attributes: "{{ item.compute_attributes }}"
        server_url: "https://sat.hostname.com"
        username: "user"
        password: "pass"
        state: "{{ item.state | default(omit) }}"
      loop: "{{ compute_profiles  | default([]) }}"
      when: compute_profiles is defined

Results:

Going to Compute Resources > test (VMware) > Compute Profiles > Edit Small shows the storage pod is set to StoragePodName.


Notes: 

Setting test coverage to - as we don't have VMware tests set up, and in this instance it would require checking a niche UI case after running a playbook. Will determine in the future if we need dedicated VMware compute profile tests in FAM.

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.