[CI] gate-nova-python27-updates get failed constantly

Bug #1490620 reported by Denis Meltsaykin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Alex Ermolov
6.0.x
Fix Released
High
Alex Ermolov
6.1.x
Invalid
Undecided
Alex Ermolov
7.0.x
Invalid
Undecided
Alex Ermolov
8.0.x
Invalid
Undecided
Alex Ermolov
Future
Invalid
Undecided
Alex Ermolov

Bug Description

Infra job on nova get failed all the time on fuel-6.0-updates branch.
http://logs.mosi.mirantis.net/20/10920/2/check/gate-nova-python27-updates/1154d31/

Tags: fuel-ci
Changed in fuel:
assignee: Fuel CI team (fuel-ci) → MOS Nova (mos-nova)
Revision history for this message
Sergey Nikitin (snikitin) wrote :

I guess the problem is in requirements. For example nova require oslo.utils >= 1.4.0 but got oslo.utils == 1.0.0. It happans because this job tried to get requirements from non existing branch refs/zuul/openstack-ci/fuel-6.0-updates/2014.2/Zad678764044a4f928fd47b22bcd00417

git fetch ssh://<email address hidden>:29418/mos-infra/mos-requirements refs/zuul/openstack-ci/fuel-6.0-updates/2014.2/Zad678764044a4f928fd47b22bcd00417
09:12:42 fatal: Couldn't find remote ref refs/zuul/openstack-ci/fuel-6.0-updates/2014.2/Zad678764044a4f928fd47b22bcd00417

And nova raise alot of import errors because of incorrect requirements. I guess someone should create that non existing branch or take requirements from some other branch.

Changed in fuel:
milestone: none → 6.0-updates
importance: Undecided → High
status: New → Confirmed
assignee: MOS Nova (mos-nova) → MOS Maintenance (mos-maintenance)
Revision history for this message
Alexey Khivin (akhivin) wrote :
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Vitaly, is maintenance team the right one to fix internal infra's problems? We always use the requirements aligned with stable/juno branch of upstream, there is nothing to do from our side.

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

After the investigation I believe I found the root cause. It's most probably in infra's "constraints" list. The olso.utils' constraint is set to inadequate value, which in turn causes that oslo.utils is not being limited in version during installation.
New constraints are being reviewed here: https://review.fuel-infra.org/#/c/10970

Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Fuel CI team (fuel-ci)
Changed in fuel:
milestone: 6.0-updates → 6.0.1
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Assign this to Alex of maintenance team, as he deals with broken nova infra jobs at the moment.
The fix is being reviewed: https://review.fuel-infra.org/#/c/13532/

Changed in fuel:
status: Confirmed → In Progress
assignee: Fuel CI (fuel-ci) → Alex Ermolov (aermolov)
Changed in fuel:
milestone: 6.0-updates → 9.0
status: In Progress → New
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

 This is a 6.0-specific bug, setting other milestones as Invalid.

Changed in fuel:
status: New → Invalid
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.