Actions
Bug #24704
closed
Update Foreman to use fog-vsphere 2.3.0
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
trivial
Triaged:
Yes
Description
PR is in that fixes the network find by id issue, lets update to fog-vsphere 2.3.0
Updated by The Foreman Bot almost 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5983 added
Updated by The Foreman Bot almost 7 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/2892 added
Updated by Ewoud Kohl van Wijngaarden almost 7 years ago
- Subject changed from Update Foreman to use new fog-vsphere gem to Update Foreman to use fog-vsphere 2.3.0
Updated by Ewoud Kohl van Wijngaarden almost 7 years ago
- Pull request https://github.com/theforeman/foreman/pull/6002 added
- Pull request deleted (
https://github.com/theforeman/foreman/pull/5983)
Updated by
Updated by The Foreman Bot almost 7 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/2918 added
Updated by Tomer Brisker almost 7 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.
Updated by Tomer Brisker almost 7 years ago
- Related to Bug #23961: Networks in a distributed switch take a long time to load when there is alot added
Updated by Tomer Brisker almost 7 years ago
- Related to Bug #24571: With fog-vsphere 2.3 trying to provision to a port group within a distributed switch fails added
Actions