Red Hat Bugzilla – Bug 1462509
LBaaS tests does not run on DFG-network-neutron-lbaas-10_director-rhel-7.3-virthost jobs
Last modified: 2017-09-06 13:17:18 EDT
Description of problem:
LBaaS tests does not run on our CI jobs
according to whitelist / blacklist it should run
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run rhos10 CI job,
As per the investigation, In neutron-lbaas OSP 10 branch, there is no 'neutron_lbaas/tests/tempest/plugin.py' file.it is a requirement for the tempest plugin.Apart from that we need to define an entry point in setup.cfg
something like that:
neutron_lbaas = neutron_lbaas.tests.tempest.plugin:NeutronLbaasTempestPlugin 
Tempest looks for "tempest.test_plugins" entrypoint in order to discover tempest plugin, if it is found it will list the plugin. The plugin.py file knows where the tempest tests related to specific project lives.
All the above things like : neither tempest_plugin entrypoint [https://github.com/openstack/neutron-lbaas/blob/stable/newton/setup.cfg#L33] and nor plugin.py file [https://github.com/openstack/neutron-lbaas/tree/stable/newton/neutron_lbaas/tests/tempest] found in stable/newton branch. That's why tempest has no clue whether there are tempest tests or not in neutron-lbaas in stable/newton or RHOS-10 branch.
So we cannnot run the neutron lbass tempest tests directly using tempest.
In order to fix the above issue, I have backported a patch review for the same: https://review.openstack.org/#/c/475193/1 which provides proper tempest plugin for neutron-lbass in newton.
Since it is not a tempest bug, so changing the component to neutron-lbaas.
fix verified :
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.