crmsh should be taken back to -main

Bug #1862947 reported by Rafael David Tinoco on 2020-02-12
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
crmsh (Ubuntu)
Status tracked in Focal
Focal
Medium
Rafael David Tinoco
pacemaker (Ubuntu)
Status tracked in Focal
Focal
Medium
Rafael David Tinoco

Bug Description

crmsh is currently the most tested cluster resource manager configuration tool we have for Ubuntu (pcs being the second one, and already scheduled for more tests in order to replace it in a near future).

With that said, currently crmsh is found at -universe:

rafaeldtinoco@workstation:~$ rmadison crmsh
 crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all
 crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all
 crmsh | 2.2.0-1 | xenial | source, ...
 crmsh | 3.0.1-3ubuntu1 | bionic/universe | source, all
 crmsh | 3.0.1-3ubuntu1 | disco/universe | source, all
 crmsh | 4.1.0-2ubuntu2 | eoan/universe | source, all
 crmsh | 4.2.0-2ubuntu1 | focal/universe | source, all

When it should be placed back in main since there is no other way to configure pacemaker other than editing manually - blergh - a CIB file for example. There's gotta to be supported way (-main) to configure clustering.

There was already a MIR for crmsh:

https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019

So I'm including crmsh as a pacemaker dependency for it to be triggered as a component mismatch. This will likely be enough after some IRC discussions with other Ubuntu developers.

Related branches

Changed in crmsh (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Rafael David Tinoco (rafaeldtinoco)
Changed in pacemaker (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Rafael David Tinoco (rafaeldtinoco)
Changed in crmsh (Ubuntu):
status: In Progress → Fix Released

I repopend the MIR bug 1205019 as this is what will show up in the component mismatches.

Correct! I missed that part. Thank you!

Acording to:

https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019/comments/10

It was proposed to main again by doko.

I'll wait full pacemaker migration - and test crmsh installation - to close this bug.

$ rmadison crmsh
 crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all
 crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all
 crmsh | 2.2.0-1 | xenial | source, ...
 crmsh | 3.0.1-3ubuntu1 | bionic/universe | source, all
 crmsh | 3.0.1-3ubuntu1 | disco/universe | source, all
 crmsh | 4.1.0-2ubuntu2 | eoan/universe | source, all
 crmsh | 4.2.0-2ubuntu1 | focal | source, all

Alright, crmsh is back on main. Waiting on pacemaker migration as it currenlty states:

pacemaker (2.0.1-5ubuntu1 to 2.0.1-5ubuntu4)
Maintainer: Ubuntu Developers
0 days old
pacemaker/amd64 unsatisfiable Depends: crmsh
pacemaker/arm64 unsatisfiable Depends: crmsh
pacemaker/armhf unsatisfiable Depends: crmsh
pacemaker/i386 unsatisfiable Depends: crmsh
pacemaker/ppc64el unsatisfiable Depends: crmsh
pacemaker/s390x unsatisfiable Depends: crmsh
Not considered

MERGE: https://code.launchpad.net/~rafaeldtinoco/britney/hints-ubuntu/+merge/379234

Will allow pacemaker migration as it will unblock bad i386 autopkgtest results.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pacemaker - 2.0.1-5ubuntu5

---------------
pacemaker (2.0.1-5ubuntu5) focal; urgency=medium

  * Fix: Last attempt i386 binary packages removal was wrong (-Nlibkate)
  * Ubuntu i386 binary compatibility only effort: (LP: #1863437)
    - i386 binary package removal:
      - pacemaker
      - pacemaker-cli-utils
      - pacemaker-remote
      - pacemaker-resource-agents

 -- Rafael David Tinoco <email address hidden> Sat, 15 Feb 2020 18:52:20 +0000

Changed in pacemaker (Ubuntu Focal):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers