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 1885240 - [RFE] Provisioning with interfaces on VMware requires portgroup
Summary: [RFE] Provisioning with interfaces on VMware requires portgroup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: 6.10.0
Assignee: Evgeni Golov
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:41 UTC by Luka Bac
Modified: 2021-11-16 14:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:09:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman-ansible-modules issues 1041 0 None open Network in vsphere vm_attrs can only be configured by hidden/internal network title (aka. network_id) 2021-02-15 08:21:00 UTC
Github theforeman foreman-ansible-modules pull 1136 0 None open lookup the correct network_id for a given network 2021-02-15 08:21:42 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:09:44 UTC

Description Luka Bac 2020-10-05 13:41:11 UTC 
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:
Comment 1 Evgeni Golov 2021-02-15 08:21:43 UTC 
There is a PR in progress at https://github.com/theforeman/foreman-ansible-modules/pull/1136 if you want to try it out :)
Comment 5 errata-xmlrpc 2021-11-16 14:09:33 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.