A new job is introduced for the purpose to cleanup
network resources before OpenStack removal.
TESTS STATUS
- After a fresh deployment of existing stx-openstack app, PASSED
check that VMs can be launched successfully
- Delete VMs and remove OpenStack, without a cleanup of PASSED
network resources. After re-deploying OpenStack, verify
that an error scenario arises where new VMs can not be
launched, with the following error message:
"nova.exception.VirtualInterfaceCreateException ...
Failed to allocate the network(s), not rescheduling".
- Load the updated charts in a fresh OpenStack re-install. PASSED
Assert that OpenStack is deployed successfully, and that
VMs can be launched successfully.
- Delete VMs and remove OpenStack, without a cleanup of PASSED
network resources. After re-deploying OpenStack, verify
that the previous error scenario does not show up and
that new VMs can be launched successfully.
- Verify that the OpenStack charts deployment-sequence PASSED
is unchanged, compared to existing codebase.
- Verify that, for all OpenStack charts, except the ones PASSED
under the compute-kit group, the removal sequence is
the reverse of deployment-sequence.
- Verify that the charts under the compute-kit group are PASSED
deployed in parallel but removed in sequence.
The removal sequence is the reverse deployment-sequence
from the OpenStack Armada App manifest.
- Verify that, within the OpenStack compute-kit group, PASSED
the Neutron chart is the first one to be removed.
Partial-Bug: 1892659
Explanatory text: this is a system improvement which aims
to prevent from similar bugs as the one above.
Signed-off-by: rferraz <RogerioOliveira.Ferraz@windriver.com>
Change-Id: I268ab75a849734874646b5f23b0bcdbe5faae1ef
b5b4cc562a