Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When doing provisioning using vmware, after selecting the cluster it shows all the ip addresses which are on vsphere.
How reproducible:
Whenever doing provisioning using VMware as deployment machine.
Steps to Reproduce:
Go to new host, start the provisioning, select the deploy on Vmware and then select Vmware cluster, in interface tab it shows all the IP address.
Actual results:
It should display network which are part of selected cluster
Expected results:
Displaying networks from all cluster which are in Vsphere environment.
Additional info:
vaguely related BZ 1218628 (Ability to search VmWare networks) has moved to verified for 6.3, but that BZ doesn't solve the use case of multiple networks across clusters with the same name. Example:
cluster 1:
VLAN_100
VLAN_101
VLAN_102
cluster 2:
VLAN_100
VLAN_101
VLAN_102
cluster 3:
VLAN_100
VLAN_101
VLAN_102
The new search function (which will be a nice addition) does not appear to solve for the above use case. It seems if they would search for "VLAN_100" they would get 3 seemingly identical networks without an understand of which is for the cluster they are deploying to. Unless there is other logic change to only display those networks on the specific cluster.
At the time of provisioning, when we select a specific cluster, Satellite displays the IP address of all the clusters, but it should display only one cluster IP's.