Description of problem: pep8 job failing on networking-ovn component CI on OSP13 branch https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/DFG-network-networking-ovn-13-pep8-rhos/9/consoleFull 10:31:17 ************* Module networking_ovn.cmd.neutron_ovn_db_sync_util 10:31:17 E: 20, 0: No name 'topics' in module 'neutron.common' (no-name-in-module) networking-ovn imports topics.py from neutron.common In upstream master branch, topics.py is removed from neutron repo and added to neutron_lib. But in queens branch, topics.py still exists in neutron repo. Looks like tox is using neutron master branch instead of queens(or osp13) branch. In my local OSP13 setup, I see tox executing below command(from tools/tox_install.sh) which is pulling master branch instead of queens. pip install -chttps://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/queens -U -e git+https://git.openstack.org/openstack/neutron@master#egg=neutron I faced the same issue when I tried locally running pep8 on upsteam queens branch, but CI pep8 job on upstream queens branch is successful. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Apparently we have the same error for stable/queens upstream, I've backported the fix here https://review.openstack.org/#/c/559046/
(In reply to Lucas Alvares Gomes from comment #1) > Apparently we have the same error for stable/queens upstream, I've > backported the fix here https://review.openstack.org/#/c/559046/ Ignore this... It just worksaround the problem. Apparently the error was in the tox_install.sh script. I've uploaded another patch to fix it at https://review.openstack.org/#/c/559066/