Bug 1885234

Summary: [RFE] Provisioning with disk requires storage_pod
Product: Red Hat Satellite Reporter: Luka Bac <lbac>
Component: Ansible CollectionAssignee: Evgeni Golov <egolov>
Status: ON_QA --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.7.0CC: egolov, gsulliva, j.becker, pbadguja, sokeeffe, zhunting
Target Milestone: streamKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ansible-collection-redhat-satellite-4.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luka Bac 2020-10-05 13:37:03 UTC
Description of problem:
When provisioning a new host, we need to specify a storage_pod or datastore to place the hard disk into.

redhat.satellite.host:
  [...]
  compute_attributes:
    volumes_attributes:
      '0':
        size_gb: '42'
        storage_pod: STORAGE_POD_NAME

However, we should allow the provider (VMware in this case) to give us a storage_pod to use for our cluster/datacenter.

If this is not feasible, then the collection should provide a facility to query for available storage_pods in the current compute_resource, similar to the https://satellite.server.com/api/compute_resources/:id/available_storage_pods API endpoint.


Example output of `hammer compute-resource storage-pods --id 1`
------------|---------
ID          | NAME    
------------|---------
group-p123  | DC-01-01
group-p234  | DC-01-02
------------|---------
Version-Release number of selected component (if applicable): 1.3.0


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Evgeni Golov 2021-03-08 12:04:27 UTC
upstream PR merged

Comment 3 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Brad Buckingham 2022-09-05 22:56:27 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Pranjal 2022-10-14 05:19:57 UTC
Hello Team,

We have another scenario where using "storage_pod" as direct value changes name to ID.
The Playbook in reference is to create "Compute Profile". Change in value affects deployment of new servers. 

Kindly consider this scenario for further check.