This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2263706 - Compute profile created through Satellite Ansible collection shows empty storage pod in web ui
Summary: Compute profile created through Satellite Ansible collection shows empty stor...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: stream
Assignee: satellite6-bugs
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-11 06:15 UTC by Hao Chang Yu
Modified: 2024-06-06 17:02 UTC (History)
6 users (show)

Fixed In Version: ansible-collection-redhat-satellite-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:02:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman-ansible-modules issues 1247 0 None closed storage_pod can not be set 2024-02-11 06:16:04 UTC
Github theforeman foreman-ansible-modules pull 1686 0 None Merged issue 1247: storage_pod from 'id' to 'name' 2024-02-11 06:16:04 UTC
Red Hat Issue Tracker   SAT-23167 0 None Migrated None 2024-06-06 17:02:21 UTC

Description Hao Chang Yu 2024-02-11 06:15:25 UTC
Description of problem:
The compute profile created through Satellite Ansible collection will set the storage pod to its id instead of name. This is causing Web UI showing empty storage pod and the image base host provisioning to fail with Storage pod doesn't exist error.

~~~
error (Foreman::WrappedException): ERF50-1679 [Foreman::WrappedException]: Satellite could not find a required vSphere resource. Check if Satellite has the required permissions and the resource exists. Reason: Storage Pod group-XXXXX Doesn't Exist! ([Fog::Vsphere::Compute::NotFound]: Storage Pod group-XXXXX Doesn't Exist!)
~~~

How reproducible:
Always

Additional info:
This is a known issue and has been fixed upstream:

Upstream issue:
https://github.com/theforeman/foreman-ansible-modules/issues/1247

Upstream PR:
https://github.com/theforeman/foreman-ansible-modules/pull/1686

Comment 1 Griffin Sullivan 2024-05-29 15:14:43 UTC
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.

Comment 2 Eric Helms 2024-06-06 17:02:23 UTC
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.


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