Bug 1885234
| Summary: | [RFE] Provisioning with disk requires storage_pod | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Luka Bac <lbac> |
| Component: | Ansible Collection | Assignee: | Evgeni Golov <egolov> |
| Status: | CLOSED MIGRATED | QA Contact: | Griffin Sullivan <gsulliva> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.7.0 | CC: | egolov, gsulliva, j.becker, pbadguja, sokeeffe, zhunting |
| Target Milestone: | stream | Keywords: | FutureFeature, MigratedToJIRA, 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: | 2024-06-06 00:36:04 UTC | 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: | |||
upstream PR merged 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. 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. 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. See https://bugzilla.redhat.com/show_bug.cgi?id=2263706#c1 for Verification Notes BTW, I also ran those steps without specifying storage_pod and it worked the same. 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. |
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: