[system_tests] [ubuntu] manage extra_deb_repos with custom priorities

Bug #1441575 reported by Bogdan Dobrelya
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Dennis Dmitriev

Bug Description

When there is some testing repo with some package under test, sys tests should be able to ensure the proper pinning for this extra deb repo.
The issue is, for example, when I'm going to test a new pacemaker build from OSCI testing repo:

EXTRA_DEB_REPOS="deb http://obs-1.mirantis.com:82/trusty-fuel-6.1-stable-5388/ubuntu /"

the pacemaker package cannot be updated due to the main MOS repo has a higher pin and pushes the older version of pacemaker.

Also, internal docs at https://mirantis.jira.com/wiki/display/PRD/External+Ubuntu+Repositories do not have details about extra_deb_repos usage.

So, please:
1) Check if it is possible to define the repo priorities for our system tests jobs
2) Fix the internal docs about how to use EXTRA_DEB_REPOS with priorities
3) Provide extra_deb_repos examples (like in the comment #3 below)
4) Make the publicly available docs at Fuel wiki/dev docs as well.

Changed in fuel:
assignee: nobody → Dennis Dmitriev (ddmitriev)
milestone: none → 6.1
status: New → Confirmed
importance: Undecided → High
Changed in fuel:
importance: High → Critical
assignee: Dennis Dmitriev (ddmitriev) → Fuel QA Team (fuel-qa)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Dennis Dmitriev (ddmitriev)
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

As far as I can see from the sys test logs http://pastebin.com/q2M7NPMm, the priorities are hardcode.

Here is an output from my lab http://pastebin.com/B8En6QDu
It reports the former extra-0 repo pin is 1050 but the real priority reported by apt-cache policy is 500, hence the pacemaker package cannot be updated to the version under test

Revision history for this message
Vitaly Parakhin (vparakhin) wrote :
Revision history for this message
Vitaly Parakhin (vparakhin) wrote :

Also, you got default pin priority for your extra repository, because it's flat.
Try to use the following value for EXTRA_DEB_REPOS:

http://obs-1.mirantis.com:82/trusty-fuel-6.1-stable-5388/reprepro/ trusty main

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Here is how it can be quick-fixed for system tests jobs (keeping pins as hardcodes)

root@node-1:~# cat /etc/apt/preferences.d/extra-0
Package: *
Pin: release a=/
Pin-Priority: 1050

Package: *
Pin: origin "*obs*mirantis*"
Pin-Priority: 1150

root@node-1:~# apt-cache policy pacemaker
pacemaker:
  Installed: 1.1.10+git20130802-1ubuntu2.3
  Candidate: 1.1.12-0ubuntu1~mos6.1+3
  Version table:
     1.1.12-0ubuntu1~mos6.1+3 0
       1150 http://obs-1.mirantis.com:82/trusty-fuel-6.1-stable-5388/ubuntu/ Packages
 *** 1.1.10+git20130802-1ubuntu2.3 0
       1050 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
       1050 /var/lib/dpkg/status
     1.1.10+git20130802-1ubuntu2 0
       1050 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

@Vitaliy, thank you, that works.
Let's please update the docs with example then

description: updated
description: updated
Changed in fuel:
importance: Critical → High
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

lowering to high as it isn't a blocker anymore

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

This one is invalid as we don't have the extra_deb_repos option anymore

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