Using the same profile name in multiple clusters will cause creating VMs that use that network name to fail #20246
Labels
affects_2.2
This issue/PR affects Ansible v2.2
bug
This issue/PR relates to a bug.
cloud
module
This issue/PR relates to a module.
ISSUE TYPE
COMPONENT NAME
ovirt_vms
ANSIBLE VERSION
CONFIGURATION
[ssh_connection]
ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
OS / ENVIRONMENT
RHEL 7.3, managing RHEL 7.3
SUMMARY
If you have a RHV/ovirt installation with the Default/Default datacenter and cluster, with the default ovirtmgmt network, and create a second datacenter/cluster, also with the default ovirtmgmt network, you cannot create VMs in the second cluster. This is because the ovirt_vms module does a lookup by name for the network, and returns the first result, so if you have network names that conflict across clusters your VM will try to attach to a network not in the correct cluster.
STEPS TO REPRODUCE
Assuming a RHV installation where you have already created the Default/Default and Custom/Custom datacenters/clusters, with hosts/storage domains/etc configured.
EXPECTED RESULTS
A VM named test should come up in the Custom cluster with a nic with the ovirtmgmt profile
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: