Project

General

Profile

Bug #19424

VMware provisioning displays all IP address

Added by Marek Hulán over 2 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
-
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Team Backlog:
Marek
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1426592

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:


Related issues

Related to Foreman - Feature #15115: Filter datastore and network selection Duplicate2016-05-20
Related to Foreman - Feature #2113: Better VMWare Datastore UIClosed

History

#1 Updated by Marek Hulán over 2 years ago

  • Subject changed from VMware provisioning displays all IP address to VMware provisioning displays all IP address
  • Target version set to 115

#2 Updated by Angelo Lisco over 2 years ago

  • Related to Feature #15115: Filter datastore and network selection added

#3 Updated by Angelo Lisco over 2 years ago

#4 Updated by Angelo Lisco over 2 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3559 added

Timo Goebel was working on a patch to filter networks and datastores depending on the cluster selection.
I also wish this could be fixed in 1.16 GA since the actual behavior (no filtering at all) it's very frustrating when you have multiple clusters and each one has different datastores and networks.

Marek Hulán wrote:

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1426592

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:

#5 Updated by Dominic Cleal over 2 years ago

  • Pull request deleted (https://github.com/theforeman/foreman/pull/3559)

#6 Updated by Angelo Lisco almost 2 years ago

I can't understand why Dominic unlinked the PR 3559 from this bug report. Yes, the PR is not complete yet but I think it's a great start for everyone who wants to work on this important feature.

Angelo Lisco wrote:

Timo Goebel was working on a patch to filter networks and datastores depending on the cluster selection.
I also wish this could be fixed in 1.16 GA since the actual behavior (no filtering at all) it's very frustrating when you have multiple clusters and each one has different datastores and networks.

Marek Hulán wrote:

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1426592

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:

#7 Updated by Marek Hulán almost 2 years ago

  • Pull request https://github.com/theforeman/foreman/pull/3559 added

I don't see the reason either, reverting. The PR is currently inactive but still open and relevant.

#8 Updated by Chris Roberts about 1 year ago

  • Triaged set to No
  • Difficulty set to medium
  • Assignee set to Timo Goebel

#9 Updated by Chris Roberts about 1 year ago

  • Triaged changed from No to Yes
  • Found in Releases 1.18.0-RC3 added

Also available in: Atom PDF