[system_tests] [ubuntu] manage extra_deb_repos with custom priorities
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_
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:/
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) |
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