Project

General

Profile

Bug #24704

Update Foreman to use fog-vsphere 2.3.0

Added by Chris Roberts about 2 years ago. Updated about 2 years ago.

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

Description

PR is in that fixes the network find by id issue, lets update to fog-vsphere 2.3.0


Related issues

Related to Foreman - Bug #23961: Networks in a distributed switch take a long time to load when there is alotClosed
Related to Foreman - Bug #24571: With fog-vsphere 2.3 trying to provision to a port group within a distributed switch failsClosed

History

#1 Updated by The Foreman Bot about 2 years ago

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

#2 Updated by The Foreman Bot about 2 years ago

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

#3 Updated by Ewoud Kohl van Wijngaarden about 2 years ago

  • Subject changed from Update Foreman to use new fog-vsphere gem to Update Foreman to use fog-vsphere 2.3.0

#4 Updated by Ewoud Kohl van Wijngaarden about 2 years ago

  • Pull request https://github.com/theforeman/foreman/pull/6002 added
  • Pull request deleted (https://github.com/theforeman/foreman/pull/5983)

#5 Updated by Ondřej Pražák about 2 years ago

  • Fixed in Releases 1.18.2 added

#6 Updated by The Foreman Bot about 2 years ago

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

#7 Updated by Tomer Brisker about 2 years ago

  • Status changed from Ready For Testing to Closed

This was merged into 1.18-stable so won't be picked up by automation.

#8 Updated by Tomer Brisker about 2 years ago

  • Related to Bug #23961: Networks in a distributed switch take a long time to load when there is alot added

#9 Updated by Tomer Brisker about 2 years ago

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

Also available in: Atom PDF