clvm startup script requires cman

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

It appears that the cman tooling isn't available in Trusty even, so this means the clvm is really broken. On >= Trusty this can be fixed by checking the corosync status (corosync-quorumtool -s) to ensure that the clustering (corosync) services are up.

Regarding your xenial debdiff the correct syntax is (LP: #1089013) to close a Launchpad bug the Closes syntax is for Debian bug reports. Additionally, the openais / dlm change is undocumented. What is that for?

Ah thanks Brian for the corrections. Here's an updated patch with the changelog indicating the change to the openais / dlm change. Hopefully its clear. In trusty the cman and openais packages were removed. Instead to setup clustered LVM one can use the distributed lock manager and corosync to manage distributed locking for the LVM vgs.

Here's an updated debdiff for xenial, I'll rework and repost the wily and trusty debdiffs as well. FTR, I didn't include a patch for vivid as it EOLs at the end of next week.

Hello,

I have sponsored your Xenial fix,; Brian's suggested modification were included.

This bug was fixed in the package lvm2 - 2.02.133-1ubuntu4

---------------
lvm2 (2.02.133-1ubuntu4) xenial; urgency=medium

  * Remove the init script dependency on cman_tool. (LP: #1089013)
    - debian/clvm.init: check corosync cluster status since the cman
      tooling isn't available in Xenial. Change start/stop dependencies
      to dlm instead of cman and openais since neither cman nor openais
      are available.

 -- Billy Olsen <email address hidden> Thu, 28 Jan 2016 11:38:39 +0100

ACK on the debdiffs in comment #9 and #10. I've uploaded them for processing by the SRU team, but I've added the missing start/stop dependencies change to the trusty one first.

Thanks!

Hello Maxxer, or anyone else affected,

Accepted lvm2 into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.02.122-1ubuntu2 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!

Hello Maxxer, or anyone else affected,

Accepted lvm2 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.02.98-6ubuntu3 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!

The wily update was not verified in three months, and wily is almost EOL. So I removed the -proposed package.

The check for corosync running doesn't work properly and prevents the clvm service from properly starting.

The version of lvm2 in the proposed pocket of Trusty that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release