constraints for the neutron-lbaas breaks queens gate jobs

Bug #1778054 reported by Boden R
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Global Requirements
Fix Released
Undecided
Boden R

Bug Description

The introduction of constraints for neutron-lbaas [1] breaks consumers who depend on neutron-lbaas as a required-project (e.g. install from src). For example [1] broke all stable/queens jobs for vmware-nsx [2] due to:

Could not satisfy constraints for 'neutron-lbaas': installation from path or url cannot be constrained to a version

As per discussion with the infra team is was suggested to update our queens branch to fully use zuul v3 (tox siblings). That was done in [3] and does fix the issue noted above. However since the required projects are not in the global-constraints for queens, the requirements-check job in [3] is failing because these required-projects are not in global constraints (see job log in [3]).

It's not clear how to proceed with [3] without these global constraints.
[4] was proposed, but as expected it fails because we don't have the projects in the upper constraints.

It's unclear how to proceed at this point.

[1] https://review.openstack.org/#/c/576526/
[2] https://review.openstack.org/#/c/576822/
[3] https://review.openstack.org/#/c/576925/
[4] https://review.openstack.org/#/c/576988/

Revision history for this message
Boden R (boden) wrote :

networking-odl appears to also be affected: https://review.openstack.org/#/c/577205/

Revision history for this message
Matthew Thode (prometheanfire) wrote :

Why do those projects need to install neutron-lbass from source?

Revision history for this message
Boden R (boden) wrote :

Matthew,
They need the projects installed from source to verify (in gate jobs) that they work properly with the latest of the respective dependency (required proj from source) as well as to access the latest source (for their internal useage of that dependency). This is a fairly common thing the infra team seems to call "tox siblings".

This works fine in master where we already have those dependent (from src) projects in the global requirements, but that isn't the case for queens.

Revision history for this message
Boden R (boden) wrote :
Changed in openstack-requirements:
status: New → Fix Released
assignee: nobody → Boden R (boden)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/requirements queens-eol

This issue was fixed in the openstack/requirements queens-eol release.

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.