CI Failing because of constant used in neutron is not found

Bug #1779825 reported by Miguel Angel Ajo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
New
Undecided
Unassigned

Bug Description

2018-07-02 15:28:23.056725 | ubuntu-xenial |
2018-07-02 15:28:23.056872 | ubuntu-xenial | Exception occurred:
2018-07-02 15:28:23.059671 | ubuntu-xenial | File "/home/zuul/.venv/local/lib/python2.7/site-packages/neutron/plugins/common/constants.py", line 28, in <module>
2018-07-02 15:28:23.059781 | ubuntu-xenial | 'router': constants.L3,
2018-07-02 15:28:23.059944 | ubuntu-xenial | AttributeError: 'module' object has no attribute 'L3'
2018-07-02 15:28:23.061892 | ubuntu-xenial | The full traceback has been saved in /tmp/sphinx-err-lEY7bK.log, if you want to report the

But if we check that in neutron/master

738aa4133c quantum/plugins/common/constants.py (Eugene Nikanorov 2013-05-03 18:57:00 +0400 21) EXT_TO_SERVICE_MAPPING = {
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 22) 'lbaas': p_const.LOADBALANCER,
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 23) 'lbaasv2': p_const.LOADBALANCERV2,
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 24) 'fwaas': p_const.FIREWALL,
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 25) 'vpnaas': p_const.VPN,
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 26) 'metering': p_const.METERING,
df6da4d6be neutron/plugins/common/constants.py (Boden R 2018-01-08 11:23:06 -0700 27) 'router': p_const.L3,
95f1e03446 neutron/plugins/common/constants.py (Boden R 2017-05-31 07:56:18 -0600 28) 'qos': p_const.QOS,
738aa4133c quantum/plugins/common/constants.py (Eugene Nikanorov 2013-05-03 18:57:00 +0400 29) }

It changed long ago.

Are we picking up an ancient version from pip for documentation?

http://logs.openstack.org/10/579210/2/check/networking-ovn-dsvm-functional/7f60674/job-output.txt.gz#_2018-07-02_15_40_07_759938

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

https://review.openstack.org/#/c/531857/

I think this is the culprit, may be this would be fine with a more recent version of neutron, or we need a new release of neutron to pypi.

https://pypi.org/project/neutron/#history

description: updated
Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

pip is installing 12.0.3 instead of something like
13.0.0.0b2

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/579856
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=45cddcbd02f8b2e45fb70816d5012605d221700c
Submitter: Zuul
Branch: master

commit 45cddcbd02f8b2e45fb70816d5012605d221700c
Author: Miguel Angel Ajo <email address hidden>
Date: Tue Jul 3 14:50:24 2018 +0200

    Use neutron 13.0.0.0b2 and don't check specific revision numbers in tests

    The neutron-lib has been recently bumped by change
    I1777349f20eff463e6d81e98d5afe9c4dc12807d in upper-constraints. This
    neutron-lib version is not compatible with Queens Neutron code.

    This patch bumps the used Neutron version to the latest beta tag. This
    should fix the failing jobs.

    Bumping to the new revision also fails our functional tests because
    we check for specific revision numbers. We can't know exactly what the
    revision number will be, so just check that it matches the neutron resource.

    Related-Bug: 1779825

    Co-Authored-By: Terry Wilson <email address hidden>

    Change-Id: I530a6e54d82daa5d1c34a026434e432c31554287

tags: added: networking-ovn-proactive-backport-potential
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.