zaza.openstack.charm_tests.neutron.tests.NeutronNetworkingTest may in some circumstances not perform a valid test #641
Comments
|
The CI test runner does not have administrator credentials to the CI cloud. So the initial thought of using specific host placement will not be practical. An alternative could be to explore the Nova server groups API |
fnordahl
added a commit
that referenced
this issue
Jan 13, 2022
Use the Nova Server Groups API to influence placement of test instances. Fixes #641
fnordahl
added a commit
that referenced
this issue
Feb 9, 2022
Use the Nova Server Groups API to influence placement of test instances. Fixes #641
fnordahl
added a commit
that referenced
this issue
Feb 9, 2022
Use the Nova Server Groups API to influence placement of test instances. Fixes #641
fnordahl
added a commit
that referenced
this issue
Jul 19, 2022
Use the Nova Server Groups API to influence placement of test instances. Fixes #641
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The premise of the
NeutronNetworkingTestis to validate end to end connectivity between two instances on two separate hypervisors. We do this by having a bundle with at least two hypervisors and requesting two instances from Nova.Nova scheduling will in most cases place the two instances on separate hypervisors, but it does not always do that. And in the cases when both instances end up on the same hypervisor the test may provide a false positive result.
The Nova API does expose mechanisms for an administrator to request specific placement of instances, and I think it would be worth to use those and assert diverse placement of instances prior to assessing connectivity.
The text was updated successfully, but these errors were encountered: