Activity log for bug #1826045

Date Who What changed Old value New value Message
2019-04-23 19:11:23 Ben Fu bug added bug
2019-04-23 19:12:15 Ben Fu summary Unsatisfiable recommended dependency pacemaker >= 2.0 Unsatisfiable recommended dependency pacemaker >= 2.0, corosync >= 3.0
2019-04-23 19:12:26 Ben Fu summary Unsatisfiable recommended dependency pacemaker >= 2.0, corosync >= 3.0 Unsatisfiable recommended dependencies pacemaker >= 2.0, corosync >= 3.0
2019-05-10 18:28:09 Launchpad Janitor pcs (Ubuntu): status New Confirmed
2019-05-10 18:44:59 Heitor Alves de Siqueira nominated for series Ubuntu Disco
2019-05-10 18:44:59 Heitor Alves de Siqueira bug task added pcs (Ubuntu Disco)
2019-05-10 18:45:07 Heitor Alves de Siqueira pcs (Ubuntu Disco): status New Confirmed
2019-05-10 18:46:24 Heitor Alves de Siqueira pcs (Ubuntu): status Confirmed Fix Released
2019-05-10 18:46:28 Heitor Alves de Siqueira pcs (Ubuntu Disco): importance Undecided High
2019-05-10 18:46:30 Heitor Alves de Siqueira pcs (Ubuntu Disco): assignee Heitor Alves de Siqueira (halves)
2019-05-10 18:46:56 Heitor Alves de Siqueira tags sts
2019-05-16 12:25:11 Heitor Alves de Siqueira 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? [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-2ubuntu1.19.04.1 | disco-security | amd64 pacemaker | 1.1.18-2ubuntu1.19.04.1 | disco-updates | amd64 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://github.com/ClusterLabs/pcs/blob/master/CHANGELOG.md#0101---2018-11-23 [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-2ubuntu1.19.04.1 is to be installed Recommends: pacemaker (>= 2.0) but 1.1.18-2ubuntu1.19.04.1 is to be installed 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?
2019-05-27 18:07:19 Eric Desrochers bug added subscriber Eric Desrochers
2019-05-28 11:02:37 Robie Basak bug added subscriber Robie Basak
2019-05-28 13:41:07 Heitor Alves de Siqueira bug added subscriber Heitor Alves de Siqueira
2019-05-28 15:40:24 Rafael David Tinoco bug added subscriber Rafael David Tinoco
2019-05-30 19:35:22 Steve Langasek pcs (Ubuntu): status Fix Released Won't Fix
2019-05-30 19:35:25 Steve Langasek pcs (Ubuntu): status Won't Fix Invalid
2019-05-31 14:17:01 Heitor Alves de Siqueira tags sts
2020-07-02 19:30:34 Steve Langasek pcs (Ubuntu Disco): status Confirmed Won't Fix