Project

General

Profile

Bug #23961

Networks in a distributed switch take a long time to load when there is alot

Added by Chris Roberts 5 months ago. Updated 2 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Compute resources - VMware
Target version:

Description

Description of problem:
Networks in a distributed switch take a long time to load when there is alot

Version-Release number of selected component (if applicable):

6.3.1
tfm-rubygem-fog-vsphere-1.7.0-1.el7sat.noarch
foreman 1.15

How reproducible:

Steps to Reproduce:
1. Install sat 6 and connect to VMware compute resource
2. Create a lot of port groups in the distributed switch
3. Watch it take forever

Actual results:

It took more than an hour/2 in the DC with 1000+ networks.
The DC with 400 networks took maybe 20 minutes.
Another one with 21 networks was almost immediate, but one with 35 networks which is over in Singapore took about 10 minutes.

Expected results:
Much faster time to load the interfaces tab then the timing above

Additional info:

Upstream issue filed here:

https://github.com/fog/fog-vsphere/issues/144


Related issues

Related to Foreman - Bug #23580: Non-clustered ESX hosts, no longer appear in host creationClosed
Related to Foreman - Bug #24571: With fog-vsphere 2.3 trying to provision to a port group within a distributed switch failsClosed
Related to Foreman - Bug #24704: Update Foreman to use fog-vsphere 2.3.0Closed

Associated revisions

Revision dc1f9cfa (diff)
Added by Chris Roberts 4 months ago

Fixes #23961 - Update Foreman Fog-Vsphere select_nic method.

History

#1 Updated by Chris Roberts 5 months ago

  • Priority changed from Normal to High
  • Assignee set to Timo Goebel
  • Status changed from New to Resolved
  • Pull request https://github.com/fog/fog-vsphere/pull/145 added

#2 Updated by Marek Hulán 5 months ago

  • Status changed from Resolved to New

This has not been resolved yet, fog-vsphere has not been released. Once it is, we need to bump the dependency in Foreman to actually fix this. Reopening, Timo are there any plans for new release?

#3 Updated by Tomer Brisker 5 months ago

  • Triaged set to Yes
  • Legacy Backlogs Release (now unused) set to 353

#4 Updated by Timo Goebel 5 months ago

I hope to fix another issue first, will do a release then and open a PR to bump fog-vsphere.

#5 Updated by The Foreman Bot 5 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5756 added

#6 Updated by The Foreman Bot 4 months ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/2728 added

#7 Updated by Chris Roberts 4 months ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#8 Updated by Marek Hulán 4 months ago

  • Fixed in Releases 1.19.0 added

Setting 1.19 for now, packaging has not been propagated to 1.18

#9 Updated by Ewoud Kohl van Wijngaarden 4 months ago

  • Related to Bug #23580: Non-clustered ESX hosts, no longer appear in host creation added

#10 Updated by The Foreman Bot 3 months ago

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

#11 Updated by The Foreman Bot 3 months ago

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

#12 Updated by Tomer Brisker 3 months ago

  • Related to Bug #24571: With fog-vsphere 2.3 trying to provision to a port group within a distributed switch fails added

#13 Updated by Tomer Brisker 2 months ago

  • Related to Bug #24704: Update Foreman to use fog-vsphere 2.3.0 added

#14 Updated by Tomer Brisker 2 months ago

  • Fixed in Releases 1.18.2 added

Also available in: Atom PDF