Hide Forgot
Description of problem: When I am running neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest tests on non-DVR environment they failed as expected. The problem is those tests should not run if the environment did not configure with DVR. We should add a mechanism that checks if DVR is configured before it runs. How reproducible: always Steps to Reproduce: 1. run the test neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest on non-DVR environment. Version-Release number of selected component (if applicable): python-neutronclient-6.1.0-1.el7ost.noarch puppet-neutron-10.3.0-2.el7ost.noarch openstack-neutron-common-10.0.0-13.el7ost.noarch openstack-neutron-openvswitch-10.0.0-13.el7ost.noarch python-neutron-10.0.0-13.el7ost.noarch openstack-neutron-10.0.0-13.el7ost.noarch python-neutron-lib-1.1.0-1.el7ost.noarch openstack-neutron-ml2-10.0.0-13.el7ost.noarch Actual results: tests failed Expected results: Tests should not run. Additional info:
This was resolved by Arie Bregman with a CI framework workaround.
Taking a look at 454203, we were planning on modifying TripleO so that it would conditionally set the new Neutron config option that exposes or hides the DVR extension, depending on weather or not the user enabled the TripleO DVR environment file. That will ensure that if TripleO was used as the installer, then Neutron will either expose or hide the DVR extension, and the correct Tempest tests will run accordingly.
I believe this should be fixed if you pull master branches for neutron, puppet-neutron and tripleo-heat-templates. This bug is probably fixed already.
Please try with latest OSP12, I think all relevant fixes should be included.
fixed verified openstack-neutron-11.0.1-4.el7ost.noarch https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/neutron-lbaas/job/DFG-network-neutron-lbaas-12_director-rhel-virthost-3cont_2comp-ipv4-vxlan/80/artifact/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462