Actions
Feature #21676
closed
Select related vmware network when selecting a subnet
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Description
As a user, when you create a new host backed by a vmware VM you have to select both the subnet and the VM network to correctly provision a VM.
This is very error prone as a lot of users forget to set the second select field correctly. This causes the hosts to not build correctly and has to be corrected manually. In addition, Foreman does not allow updating the VM right now (#18304).
The VMWare network matching the subnet should be selected automatically when the subnet is changed.
Updated by The Foreman Bot about 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5009 added
Updated by Timo Goebel about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e69b62cec455e82052d7b78238495166ea9de773.
Updated by Daniel Lobato Garcia about 7 years ago
- Translation missing: en.field_release set to 296
Updated by Marek Hulán over 5 years ago
- Related to Bug #26280: The network used is different from the one visible in the network modal. added
Updated by Marek Hulán over 5 years ago
- Related to Bug #26307: Vmware network comming from subnet guess should not rewrite the one selected on compute profile added
Updated by Ondřej Ezr almost 4 years ago
- Related to Feature #31408: Improve selecting of related network to subnet VLAN ID added
Actions