[SRU] crmsh in vivid/wily/xenial is not compatible with pacemaker

Bug #1445616 reported by Sergii Golovatiuk
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
crmsh (Ubuntu)
Fix Released
High
James Page
Wily
Fix Committed
High
James Page
pacemaker (Ubuntu)
Fix Released
Medium
James Page
Wily
Won't Fix
Undecided
Unassigned

Bug Description

[Impact]
crmsh is currently un-usable with pacemaker/corosync in wily

[Test Case]
sudo apt-get install pacemaker corosync crmsh
[configure corosync]
[configure cluster resources using crmsh]
ERROR: CIB not supported: validator 'pacemaker-2.0', release '3.0.9'

[Regression Potential]
Right now crmsh is non-functional; 2.1.x is know to work, so moving to 2.1.4 which I uploaded earlier in the Xenial release cycle is a sensible resolution to this problem. I've tested via PPA and was successfully able to build clustered services using glance + the hacluster charms for Juju.

[Original Bug Report]
pacemaker package in vivid was updated to 1.12 which provides a new structure in CIB. However crmsh is still old which means

https://github.com/ClusterLabs/pacemaker/blob/Pacemaker-1.1.12/include/crm/cib.h#L31 contains 2.0 which result in cIb as

<cib epoch="137" num_updates="4565" admin_epoch="0" validate-with="pacemaker-2.0" crm_feature_set="3.0.9"

/usr/sbin/crm configure show xml returns
ERROR: CIB not supported: validator 'pacemaker-2.0', release '3.0.9'

Looking at https://github.com/ClusterLabs/crmsh/blob/1.2.6/modules/cibconfig.py#L2103 I can confirm that regexp is wrong

Version 2.1.3 has a proper regexp https://github.com/ClusterLabs/crmsh/blob/2.1.3/modules/cibconfig.py#L2136

Also, I can see that debian/control in pacemaker doesn't specify the minimal version of crmsh which should be higher than 2.X
crmsh (>= $version_which_understands_cib2.0)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in crmsh (Ubuntu):
status: New → Confirmed
Revision history for this message
György Szombathelyi (gyurco) wrote :

It is also wrong in Wily.

Revision history for this message
Malte Langermann (mlangermann) wrote :

It is also wrong in Xenial.

PÁLFALVI Tamás (pt314)
summary: - crmsh in vivid is not compatible with pacemaker
+ crmsh in vivid/wily/xenial is not compatible with pacemaker
Robie Basak (racb)
Changed in crmsh (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Shaheed Haque (srhaque-i) wrote : Re: crmsh in vivid/wily/xenial is not compatible with pacemaker

What are the chances of a fix/backport to vivid et. al.? Not having crmsh to set pacemaker up makes pacemaker and thus HA unusable...

Revision history for this message
David Ames (thedac) wrote :

This is affecting OpenStack HA deployments and testing for liberty

James Page (james-page)
Changed in crmsh (Ubuntu):
assignee: nobody → James Page (james-page)
status: Triaged → In Progress
James Page (james-page)
Changed in pacemaker (Ubuntu):
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → James Page (james-page)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package crmsh - 2.1.4-0ubuntu1

---------------
crmsh (2.1.4-0ubuntu1) xenial; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - d/control: Build-depend on libcib4-dev.
    - d/control: Architecture: all, not any.
    - d/control,rules: Drop BD on hardening-wrapper, tweak rules.
    - d/control: Bumped Standards-Version to 3.9.6, no changes.
  * Dropped changes, included in Debian:
    - Port from python-support to dh_python2.
  * d/control,copyright: Update for new upstream source location.
  * d/watch: Add watch file to monitor github.com releases.
  * New upstream release (LP: #1445616).
    - d/rules: Tidy for new release.
  * d/rules: Enable parallel build option.
  * d/*: Wrap and sort to help with maintenance.

crmsh (1.2.6+git+e77add-1.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Port from python-support to dh_python2 (Closes: #785973)

 -- James Page <email address hidden> Mon, 04 Jan 2016 09:49:00 +0000

Changed in crmsh (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
James Page (james-page) wrote :

The minor pacemaker update is currently tangled with the perl update in xenial; once that gets cleared, it will promote to the release pocket OK.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pacemaker - 1.1.12-0ubuntu3

---------------
pacemaker (1.1.12-0ubuntu3) xenial; urgency=medium

  * d/control: Bump minimum version on crmsh to 2.1.3 (LP: #1445616).

 -- James Page <email address hidden> Mon, 04 Jan 2016 11:28:33 +0000

Changed in pacemaker (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
James Page (james-page) wrote :

vivid is EOL this month, so lets not worry about fixing this for 15.04; but we do need to decide what todo with 15.10

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

AFAICT, for the current xenial, the pacemaker is 1.1.14 and crmsh v2.1.4 is "old" again. Works for me with https://launchpad.net/ubuntu/+source/crmsh/2.2.0-1/+build/8964914/+files/crmsh_2.2.0-1_amd64.deb

Revision history for this message
James Page (james-page) wrote : Re: [Bug 1445616] Re: crmsh in vivid/wily/xenial is not compatible with pacemaker

You should be gettting 2.2.0 in xenial:

 crmsh | 2.2.0-1 | xenial | source, amd64,
arm64, armhf, i386, powerpc, ppc64el, s390x

On Mon, 22 Feb 2016 at 09:30 Bogdan Dobrelya <email address hidden> wrote:

> AFAICT, for the current xenial, the pacemaker is 1.1.14 and crmsh v2.1.4
> is "old" again. Works for me with
>
> https://launchpad.net/ubuntu/+source/crmsh/2.2.0-1/+build/8964914/+files/crmsh_2.2.0-1_amd64.deb
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1445616
>
> Title:
> crmsh in vivid/wily/xenial is not compatible with pacemaker
>
> Status in crmsh package in Ubuntu:
> Fix Released
> Status in pacemaker package in Ubuntu:
> Fix Released
>
> Bug description:
> pacemaker package in vivid was updated to 1.12 which provides a new
> structure in CIB. However crmsh is still old which means
>
>
> https://github.com/ClusterLabs/pacemaker/blob/Pacemaker-1.1.12/include/crm/cib.h#L31
> contains 2.0 which result in cIb as
>
> <cib epoch="137" num_updates="4565" admin_epoch="0" validate-
> with="pacemaker-2.0" crm_feature_set="3.0.9"
>
> /usr/sbin/crm configure show xml returns
> ERROR: CIB not supported: validator 'pacemaker-2.0', release '3.0.9'
>
> Looking at
>
> https://github.com/ClusterLabs/crmsh/blob/1.2.6/modules/cibconfig.py#L2103
> I can confirm that regexp is wrong
>
> Version 2.1.3 has a proper regexp
>
> https://github.com/ClusterLabs/crmsh/blob/2.1.3/modules/cibconfig.py#L2136
>
> Also, I can see that debian/control in pacemaker doesn't specify the
> minimal version of crmsh which should be higher than 2.X
> crmsh (>= $version_which_understands_cib2.0)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1445616/+subscriptions
>

Revision history for this message
Anon (akq62811) wrote : Re: crmsh in vivid/wily/xenial is not compatible with pacemaker

A fix for Wily would be very much appreciated: doing a release upgrade in production servers right after a launch date is risky business as the bugs that cause most trouble use to get fixed in the first months of adoption.

Revision history for this message
Mark Haney (mark-haney-t) wrote :

I'd love a Wily fix as well. This is preventing me from moving forward on a project to load balance my web servers.

James Page (james-page)
Changed in pacemaker (Ubuntu Wily):
status: New → Invalid
Changed in crmsh (Ubuntu Wily):
status: New → Triaged
importance: Undecided → High
assignee: nobody → James Page (james-page)
Revision history for this message
James Page (james-page) wrote :

I've uploaded a backport of 2.1.4 to:

  ppa:james-page/wily

I've done some testing using our reference ha bundles for OpenStack and it tests out OK.

description: updated
summary: - crmsh in vivid/wily/xenial is not compatible with pacemaker
+ [MIR] crmsh in vivid/wily/xenial is not compatible with pacemaker
Changed in pacemaker (Ubuntu Wily):
status: Invalid → Won't Fix
James Page (james-page)
summary: - [MIR] crmsh in vivid/wily/xenial is not compatible with pacemaker
+ [SRU] crmsh in vivid/wily/xenial is not compatible with pacemaker
Revision history for this message
Martin Pitt (pitti) wrote :

Does the crmsh wily SRU still actually make sense? Non-LTS releases aren't very interesting on servers in the first place, and now that Xenial is out and wily only has two more months to live the effort/benefit ratio is even higher.

Revision history for this message
Steve Langasek (vorlon) wrote :

Since crmsh depends on pacemaker and is therefore completely unusable in wily due to this incompatibility, the risk of regression is minimal, so I'll accept this into wily-proposed. Please be sure to handle the SRU verification so that this doesn't get stalled there.

Changed in crmsh (Ubuntu Wily):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Sergii, or anyone else affected,

Accepted crmsh into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crmsh/2.1.4-0ubuntu0.15.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers