Bug 1885240
| Summary: | [RFE] Provisioning with interfaces on VMware requires portgroup | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Luka Bac <lbac> |
| Component: | Ansible Collection | Assignee: | Evgeni Golov <egolov> |
| Status: | CLOSED ERRATA | QA Contact: | Vladimír Sedmík <vsedmik> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.7.0 | CC: | egolov, ehelms, sokeeffe, zhunting |
| Target Milestone: | 6.10.0 | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 14:09:33 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: | |||
There is a PR in progress at https://github.com/theforeman/foreman-ansible-modules/pull/1136 if you want to try it out :) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702 |
Description of problem: When provisioning a new host through VMware with interfaces, currently it is required to specify a (distributed vswitch) portgroup name like so: redhat.satellite.host: [...] interfaces_attributes: '0': network: "dvportgroup-123" type: "VMXNet" This is not ideal, since it does not include any easily identifiable information, nor any VLAN information. When trying to provision through the Satellite UI, Satellite queries the vCenter for the information regarding the portgroups and provides a name for them as well. This functionality (and hammer-cli) uses the https://satellite.server.com/api/compute_resources/:id/available_networks API endpoint. The output from hammer looks something like this: ---------------------|------------------------------------------- ID | NAME ---------------------|------------------------------------------- [...] dvportgroup-123 | GER-DC3-02-v01-VLAN987 dvportgroup-456 | GER-DC3-02-v01-VLAN765 dvportgroup-789 | GER-DC3-02-v01-VLAN432 [...] We would like to be able to use this network name when provisioning a new host. If that is not feasible, we would like for the Red Hat Satellite collection to provide functionality to translate this this friendly network name into a portgroup. (or get the same name/portgroup mapping as the API) Our current workaround is to use the vmware collection to query VMware for the required information, which is not ideal and has its own drawbacks. 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: