Extra and main ubuntu repos priority issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ihor Kalnytskyi | ||
6.0.x |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When some extra Ubuntu repo is added in UI with some priority, deployed Ubuntu nodes show unexpected priorities in apt-cache policy output. For example (see attached screenshot), the external repo is:
# cat /etc/apt/
deb http://
# cat /etc/apt/
Package: *
Pin: release a=trusty,c=main
Pin-Priority: 1150
# apt-cache policy corosync
corosync:
Installed: 2.3.3-1ubuntu1
Candidate: 2.3.3-1ubuntu1
Version table:
2.
500 http://
*** 2.3.3-1ubuntu1 0
1100 http://
100 /var/lib/
But if I changed the preferences pinning to:
# cat /etc/apt/
Package: *
Pin: release n=trusty*
Pin-Priority: 1150
It would show an expected candidate now:
# apt-cache policy corosync
corosync:
Installed: 2.3.3-1ubuntu1
Candidate: 2.3.4-0u~
Package pin: 2.3.4-0u~
Version table:
2.
500 http://
*** 2.3.3-1ubuntu1 1150
1100 http://
100 /var/lib/
Changed in fuel: | |
assignee: | MOS Linux (mos-linux) → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Vladimir Kozhukalov (kozhukalov) → Igor Kalnitsky (ikalnitsky) |
status: | New → In Progress |
Note, this issue may be not valid for official mirrors, but our QA team should have a clearly documented way to test OBS test repos