Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
High
|
Heitor Alves de Siqueira |
Bug Description
[Impact]
pcs can't be used for pacemaker and corosync in Disco
[Description]
In Disco, it looks like pcs was updated to version 0.10 without an accompanying update to pacemaker and corosync. From the pcs-0.10 changelog [0]:
- Pcs-0.10 removes support for CMAN, Corosync 1.x, Corosync 2.x and Pacemaker 1.x based clusters. For managing those clusters use pcs-0.9.x.
Looking at the current versions for corosync and pacemaker in Disco, we can see that they are not supported by this pcs version:
$ rmadison -a amd64 corosync | grep disco
corosync | 2.4.4-3 | disco | amd64
$ rmadison -a amd64 pacemaker | grep disco
pacemaker | 1.1.18-2ubuntu1 | disco | amd64
pacemaker | 1.1.18-
pacemaker | 1.1.18-
Instead of upgrading pacemaker and corosync, with the risk of introducing lots of untested issues, we should consider rolling pcs back to an already tested version such as 0.9.x.
[0] https:/
[Test Case]
Try to install pacemaker and pcs at the same time in Disco:
root@disco:~# apt install pacemaker pcs
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pcs : Breaks: pacemaker (< 2.0) but 1.1.18-
Recommends: pacemaker (>= 2.0) but 1.1.18-
E: Unable to correct problems, you have held broken packages.
[Regression Potential]
The regression potential should be low, as long as we correctly roll pcs back to a previously tested version. Since corosync/pacemaker packages were not updated, this shouldn't introduce any new regressions. We'll do diligent testing with autopkgtest for any other problems.
# # # #
[Original Description]
The current version of pcs in disco is 0.10.x, which requires pacemaker >= 2.0 and corosync >=3.0, neither of which are available yet. Should the version be downgraded to 0.9.x until the other packages are updated?
summary: |
- Unsatisfiable recommended dependency pacemaker >= 2.0 + Unsatisfiable recommended dependency pacemaker >= 2.0, corosync >= 3.0 |
summary: |
- Unsatisfiable recommended dependency pacemaker >= 2.0, corosync >= 3.0 + Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0 |
Changed in pcs (Ubuntu Disco): | |
status: | New → Confirmed |
Changed in pcs (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in pcs (Ubuntu Disco): | |
importance: | Undecided → High |
assignee: | nobody → Heitor Alves de Siqueira (halves) |
tags: | added: sts |
description: | updated |
Changed in pcs (Ubuntu): | |
status: | Fix Released → Won't Fix |
status: | Won't Fix → Invalid |
tags: | removed: sts |
Changed in pcs (Ubuntu Disco): | |
status: | Confirmed → Won't Fix |
Status changed to 'Confirmed' because the bug affects multiple users.