A recent code change in NetworkManager causes NullPointerExceptions when DHCP
capability list is null.
The commit which made the NetworkManager change also changed the VirtualRouter
to not use null for the capabilitylist, but didn't make this change for other
network devices, causing DHCP to fail on MidoNet.
This change also updates the MidoNet plugin to use the most recent MidoNet API.
Signed-off-by: Sheng Yang <sheng.yang@citrix.com>
deployment fails with error "Message: Invalid configuration for device
'2'."
ensuring that direct network guru assigns a mac address for the nic that
it designs
While upgrading to 4.2 to support existing clusters working over standard vswitch or nexus dvswitch should be supported as is. To ensure this while upgrading to 4.2, existing cluster's vswitch configuration needs to be persisted to database. If zone level traffic label is empty then default vswitch name would be used.
Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
Improving the error message saying no ssh key pair is assinged to VM to get the encrypted password and included a check for password enabled template
Signed-off-by: Koushik Das <koushik@apache.org>
egressdefaultpolicy parameter was not set in base.py. Therefore
egress test failed. Added this missing change.
Signed-off-by: Jayapal <jayapal@apache.org>
Libvirt reports:
org.libvirt.LibvirtException: Storage volume not found: no storage vol
with matching name
in some cases, if the volume is created on one kvm host, while accessed
from other host.
It's possible due to concurrent access(read/write) storage.
The current fix is to try serveral times, and wait for 30 seconds for
each retry.
If the issue still there, then need to sync the storage pool access
If VSM is active, and either traffic overrides are checked, make VSM
fields required.
** This creates new VSM fields, with '_req' appended to end of ID. API
calls need to be changes to account for this.
affinity groups as admin. There are few reason why this needs to be changed and
the reasons are as mentioned below
1. we usually create an account for each test and we run the test as the newly
created account and not as admin.
2. tests were failing during deployVirtualMachine step when they are run as
admin and if anyone during these tests create an additional isolated networks
as admin account .
(P.S: current deployVirtualMachine in the scripts is not taking the networkId
and hence it fails when there are multiple isolated networks because it doesn't
know which one to pick)
Signed-off-by: venkataswamybabu budumuru <venkataswamybabu.budumuru@citrix.com>