9.0-pkg-systest-ubuntu failed due to repos priority issue

Bug #1654993 reported by Anton Chevychalov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Dmitry Burmistrov

Bug Description

Failed test:
===========
https://packaging-ci.infra.mirantis.net/job/9.0-pkg-systest-ubuntu/2606/

Description:
============
Fix https://review.fuel-infra.org/#/c/29303/ had been merged and exists in 9.0 holdback repo in package puppet-3.8.5-2~u14.04+mos2

But due to priority of repos we have puppet-common-3.8.5-2~u14.04+mos1 installed from snapshot http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/snapshots/9.0-2017-01-07-125941/

fuel-agent-env-1.log from master
================================
Get:22 http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/snapshots/9.0-2017-01-07-125941/ mos9.0/main puppet-common all 3.8.5-2~u14.04+mos1 [1026 kB]
Get:23 http://archive.ubuntu.com/ubuntu/ trusty/main libpython-stdlib amd64 2.7.5-5ubuntu3 [7012 B]
Get:24 http://archive.ubuntu.com/ubuntu/ trusty/main python amd64 2.7.5-5ubuntu3 [134 kB]

Priority information fro cluster:
=================================
  - name: mos-holdback
    priority: 1100
    section: main restricted
    suite: mos9.0-holdback
    type: deb
    uri: http://mirror.fuel-infra.org/mos-repos/ubuntu/9.0/
  - name: Auxiliary
    priority: 1150
    section: main restricted
    suite: auxiliary
    type: deb
    uri: http://10.109.0.2:8080/mitaka-9.0/ubuntu/auxiliary
  - name: extra-0
    priority: 1200
    section: main restricted
    suite: mos9.0
    type: deb
    uri: http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/snapshots/9.0-2017-01-07-125941
  - name: extra-1
    priority: 1201
    section: main restricted
    suite: mos9.0-security
    type: deb
    uri: http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/snapshots/9.0-2017-01-07-125941
  - name: extra-2
    priority: 1201
    section: main restricted
    suite: mos9.0-updates
    type: deb
    uri: http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/snapshots/9.0-2017-01-07-125941

Changed in fuel:
milestone: none → 9.2
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Anton Chevychalov (achevychalov) wrote :

Possible solution is removing of extra-0 repo.

Roman Vyalov (r0mikiam)
Changed in fuel:
status: Confirmed → New
assignee: nobody → Alexander Evseev (aevseev-h)
Changed in fuel:
status: New → In Progress
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to fuel-infra/jenkins-jobs (master)

Fix proposed to branch: master
Change author: Alexander Evseev <email address hidden>
Review: https://review.fuel-infra.org/29687

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to fuel-infra/jenkins-jobs (master)

Reviewed: https://review.fuel-infra.org/29687
Submitter: Alexander Evseev <email address hidden>
Branch: master

Commit: 25cf5f3429af80efcb02554e1c98166c344c4721
Author: Alexander Evseev <email address hidden>
Date: Mon Jan 9 12:54:31 2017

[pkgs-ci] Fix repos for Ubuntu systest

  - restore accidentaly removed proposed repo
  - add holdback repo
  - set same priority to all extra repositories to use newest available
    packages

Change-Id: Ib4f25989dce33b759fdaceaebb1343829a2458d0
Closes-Bug: #1654993

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Alexander Evseev (aevseev) wrote :

Dima, it's need to add holdback to EXTRAREPO list

Changed in fuel:
status: Fix Committed → Confirmed
assignee: Alexander Evseev (aevseev-h) → Dmitry Burmistrov (dburmistrov)
Revision history for this message
Alexander Evseev (aevseev) wrote :

I mean perestroika

Revision history for this message
Alexander Evseev (aevseev) wrote :

Timer-triggered jobs fixed by above change.
Per-CR tests are using different repo priorities, so holdback is not needed in EXTRAREPO.

Changed in fuel:
status: Confirmed → Fix Released
Revision history for this message
Alexander Evseev (aevseev) wrote :
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.