[remove] redhat-cluster

Bug #1205107 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
redhat-cluster (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Please remove redhat-cluster and its binaries from Saucy.

redhat-cluster has been made obsolete in upstream for quite a while sometime in favor of corosync/pacemaker based clusters. With the upload of the newer corosync version (> 2.X), redhat-cluster FTBFS, as it won't be able to find the necessary libraries.

redhat-cluster (or cluster as known in redhat based distributions) has been made obsolete for the past 3 Fedora releases (Fedora 19, 18, 17) and it is time for us to drop it.

More importantly, upstream no longer recommends nor supports the use of redhat-cluster (cman, rgmanager, etc), but does recommend and support clusters based on corosync/pacemaker only.

Changed in redhat-cluster (Ubuntu):
importance: Undecided → High
summary: - Please remove redhat-cluster
+ [remove] redhat-cluster
Revision history for this message
Matthias Klose (doko) wrote :

there are still a lot of build dependencies on this package. please identify these first and get rid of them

Changed in redhat-cluster (Ubuntu):
status: New → Incomplete
Revision history for this message
Adam Conrad (adconrad) wrote :

Is there a migration strategy at all for people who have these packages installed?

Revision history for this message
Stéphane Graber (stgraber) wrote :

So it looks like the following packages would need to be changed before we pull redhat-cluster from the archive:
system-config-cluster (recommend)
qpidd
pacemaker
libcrmcluster1

Most of the others listed by reverse-depends already have conditional depends/recommends that should work fine.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi All,

Thank you for your comments. A few remarks

@Adam, there is a migration plan that will involve a manual migration plan. We don't really expect people to be using cman+rgmanager in precise because it had been deprecated by upstream a very long time ago and was not recommend. However, if they are we will be providing transitional packages for upgrades to install corosync+pacemaker. However, they will have to reconfigure their clusters. As far those using pacemaker+cman+corosync or pacemaker+corosync, upgrades should work just fine, but might require a minimal configuration change.

Unfortunately, we've discussed this with upstream in Copenhagen and they told us "Sorry!! we are breaking the upgrade path, so those who want to upgrade would require manual configuration." So we will providing a guide for upgrading resources.

@Stephane:

system-config-cluster -> should be removed as well.
qpidd -> already looked into it and we should drop support to build with 'cpg' or upgrade to the latest release.
pacemaker/libcrmcluster1 -> done already, the package is sitting in -proposed waiting on 'crmsh' binary to be processed from the NEW queue as well as the MIR.

clvm -> clvm not only depends on libcman-dev but also on libdml-dev. libcman-dev can be easily dropped and only build clvm support for 'corosync'. However, there seems to be an issue with the packaging that FTBFS if try to do so, which doesn't happen if I build locally. As far as libdlm-dev, there's a new source package in the NEW queue (dlm) which provides this binary package. Upstream split the 'dlm' from redhat-cluster long ago, but now that we are dropping it, we need it.

So the idea here is to disable clvm for the time being until all the stack gets release, and we can re-enable clvm.

Hope this information helps.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

All,

So I have filed a removal bug for system-config-cluster [1].

I've made a new upload for lvm2 to disable clvm, which is what required build-depds from the redhat-cluster source package. [2]

Finally, I've also made a new upload for qpid-cpp disabling the support for 'cpg' which required build-deps from redhat-cluster as well. [3].

With this, I believe redhat-cluster can be removed, so that corosync won't be blocked. This would allow corosync to land into the archives (currently sits in -proposed).

Cheers.

[1]: https://bugs.launchpad.net/ubuntu/+source/system-config-cluster/+bug/1205438
[2]: https://launchpad.net/ubuntu/+source/lvm2/2.02.98-1ubuntu3
[3]: https://launchpad.net/ubuntu/+source/qpid-cpp/0.16-7ubuntu3

Changed in redhat-cluster (Ubuntu):
status: Incomplete → New
Revision history for this message
Dave Walker (davewalker) wrote :

Removing packages from saucy:
 redhat-cluster 3.1.8-1.1 in saucy
  cman 3.1.8-1.1 in saucy amd64
  cman 3.1.8-1.1 in saucy armhf
  cman 3.1.8-1.1 in saucy i386
  cman 3.1.8-1.1 in saucy powerpc
  libccs-dev 3.1.8-1.1 in saucy amd64
  libccs-dev 3.1.8-1.1 in saucy armhf
  libccs-dev 3.1.8-1.1 in saucy i386
  libccs-dev 3.1.8-1.1 in saucy powerpc
  libccs-perl 3.1.8-1.1 in saucy amd64
  libccs-perl 3.1.8-1.1 in saucy armhf
  libccs-perl 3.1.8-1.1 in saucy i386
  libccs-perl 3.1.8-1.1 in saucy powerpc
  libccs3 3.1.8-1.1 in saucy amd64
  libccs3 3.1.8-1.1 in saucy armhf
  libccs3 3.1.8-1.1 in saucy i386
  libccs3 3.1.8-1.1 in saucy powerpc
  libcman-dev 3.1.8-1.1 in saucy amd64
  libcman-dev 3.1.8-1.1 in saucy armhf
  libcman-dev 3.1.8-1.1 in saucy i386
  libcman-dev 3.1.8-1.1 in saucy powerpc
  libcman3 3.1.8-1.1 in saucy amd64
  libcman3 3.1.8-1.1 in saucy armhf
  libcman3 3.1.8-1.1 in saucy i386
  libcman3 3.1.8-1.1 in saucy powerpc
  libdlm-dev 3.1.8-1.1 in saucy amd64
  libdlm-dev 3.1.8-1.1 in saucy armhf
  libdlm-dev 3.1.8-1.1 in saucy i386
  libdlm-dev 3.1.8-1.1 in saucy powerpc
  libdlm3 3.1.8-1.1 in saucy amd64
  libdlm3 3.1.8-1.1 in saucy armhf
  libdlm3 3.1.8-1.1 in saucy i386
  libdlm3 3.1.8-1.1 in saucy powerpc
  libdlmcontrol-dev 3.1.8-1.1 in saucy amd64
  libdlmcontrol-dev 3.1.8-1.1 in saucy armhf
  libdlmcontrol-dev 3.1.8-1.1 in saucy i386
  libdlmcontrol-dev 3.1.8-1.1 in saucy powerpc
  libdlmcontrol3 3.1.8-1.1 in saucy amd64
  libdlmcontrol3 3.1.8-1.1 in saucy armhf
  libdlmcontrol3 3.1.8-1.1 in saucy i386
  libdlmcontrol3 3.1.8-1.1 in saucy powerpc
  libfence-dev 3.1.8-1.1 in saucy amd64
  libfence-dev 3.1.8-1.1 in saucy armhf
  libfence-dev 3.1.8-1.1 in saucy i386
  libfence-dev 3.1.8-1.1 in saucy powerpc
  libfence4 3.1.8-1.1 in saucy amd64
  libfence4 3.1.8-1.1 in saucy armhf
  libfence4 3.1.8-1.1 in saucy i386
  libfence4 3.1.8-1.1 in saucy powerpc
  liblogthread-dev 3.1.8-1.1 in saucy amd64
  liblogthread-dev 3.1.8-1.1 in saucy armhf
  liblogthread-dev 3.1.8-1.1 in saucy i386
  liblogthread-dev 3.1.8-1.1 in saucy powerpc
  liblogthread3 3.1.8-1.1 in saucy amd64
  liblogthread3 3.1.8-1.1 in saucy armhf
  liblogthread3 3.1.8-1.1 in saucy i386
  liblogthread3 3.1.8-1.1 in saucy powerpc
  redhat-cluster-suite 3.1.8-1.1 in saucy amd64
  redhat-cluster-suite 3.1.8-1.1 in saucy armhf
  redhat-cluster-suite 3.1.8-1.1 in saucy i386
  redhat-cluster-suite 3.1.8-1.1 in saucy powerpc
  rgmanager 3.1.8-1.1 in saucy amd64
  rgmanager 3.1.8-1.1 in saucy armhf
  rgmanager 3.1.8-1.1 in saucy i386
  rgmanager 3.1.8-1.1 in saucy powerpc
1 package successfully removed.

Changed in redhat-cluster (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.