Another scenario: 1. Create new environment with VLAN segmentation for Neutron 2. Add controller and compute nodes
The corresponding failed tests: https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ovs_firewall_with_dpdk/51/testReport/(root)/deploy_ovs_firewall_and_dpdk_vlan/deploy_ovs_firewall_and_dpdk_vlan/ https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.ovs_firewall_with_dpdk/51/testReport/(root)/deploy_ovs_firewall_and_dpdk_vxlan/deploy_ovs_firewall_and_dpdk_vxlan/
On failed node mcollective is not started. The restart of node fixs problem
Another scenario:
1. Create new environment with VLAN segmentation for Neutron
2. Add controller and compute nodes
The corresponding failed tests: /product- ci.infra. mirantis. net/job/ 10.0.system_ test.ubuntu. ovs_firewall_ with_dpdk/ 51/testReport/ (root)/ deploy_ ovs_firewall_ and_dpdk_ vlan/deploy_ ovs_firewall_ and_dpdk_ vlan/ /product- ci.infra. mirantis. net/job/ 10.0.system_ test.ubuntu. ovs_firewall_ with_dpdk/ 51/testReport/ (root)/ deploy_ ovs_firewall_ and_dpdk_ vxlan/deploy_ ovs_firewall_ and_dpdk_ vxlan/
https:/
https:/
On failed node mcollective is not started. The restart of node fixs problem