OCF Resource Agent "Filesystem" is still CMAN dependent

[tonyw]

The script /usr/lib/ocf/resource.d/heartbeat/Filesystem is used as part of the pacemaker system to mount disks, especially those on shared filesystems.

In the version of the script provided with 14.04, when the filesystem is of type "ocfs2", the script incorrectly checks that the HA_cluster_type is "cman". However is no longer used with 14.04. The script thus fails with the error "<your device>: ocfs2 is not compatible with your environment."

The script should instead have checked to ensure that the HA_cluster_type is set to "corosync".

The following patch needs to be applied to correct the error:

--- Filesystem 2013-12-16 07:41:25.000000000 +0000
+++ Filesystem.new 2015-01-19 19:01:30.181772112 +0000
@@ -338,7 +338,7 @@ ocfs2_init()
  # not need this:

  OCFS2_SLES10=""
- if [ "X$HA_cluster_type" = "Xcman" ]; then
+ if [ "X$HA_cluster_type" = "Xcorosync" ]; then
      return
  elif [ "X$HA_cluster_type" != "Xopenais" ]; then
   if grep -q "SUSE Linux Enterprise Server 10" /etc/SuSE-release >/dev/null 2>&1 ; then

[Launchpad Janitor (janitor)]

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

[Beat (beat-c)]

I had also the error "ocfs2 is not compatible with your environment." when trying to start it with the default Pacemaker, Corosync and ocfs2-tools under Ubuntu 16.04.2 LTS.

This was the case both using console crm and LCMC.

Confirming that this patch fixed the bug and that now it starts fine under Pacemaker/Corosync.

This should imho really be included with the next upgrade of ocfs2-tools in Ubuntu 16.04 LTS.

[Beat (beat-c)]

This bug is also there in Ubuntu 14.04 LTS.

And this patch also fixes it in Ubuntu 14.04. Should imho be included with the next upgrade of ocfs2-tools in Ubuntu 14.04 LTS too.

[Nish Aravamudan (nacc)]

In 2013, resource-agents upstream changed their code:

https://github.com/ClusterLabs/resource-agents/commit/8a0e21b4f25efd83b962bfe7195a80e608e708fd

and then all of that code was then removed in upstream as being for SLES10 only... https://github.com/ClusterLabs/resource-agents/commit/a753a0fdfad2e439ad80d2c962ce1bce452f27a5

such that the patch in $description should not be necessary and does not appear to be apply to the code in 16.04.

@beat-c can you provide the output of `apt policy resource-agents` which is what actually provides the file in question in this bug? I do not understand

I agree that the upstream fix available in 16.04 might be worth backporting to 14.04 since that is before the code was removed (it seems). I would prefer we used that patch rather than the one in $description, functionally-equivalent but a backport rather than a diversion from upstream.

[Nec (nicolas-ecarnot)]

Hello,

As I'm witnessing the exact same issue and workaround, but in the Oracle Linux world, I'm reporting the same issue.
On my nodes, the package is : resource-agents-3.9.5-105.el7.x86_64

My 2 cents...

Peace.

[Lucas Kanashiro (lucaskanashiro)]

As stated in comment #4, this bug seems to no apply to Ubuntu Xenial and Ubuntu Trusty already reached end of standard support a couple of years ago. Due to that I am removing the server-next tag and unsubscribing ubuntu-server from this bug.