The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic

Bug #1927712 reported by David Lechevalier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resource-agents (Ubuntu)
New
Undecided
Unassigned

Bug Description

Pacemaker on Ubuntu 18.04 is not able to create a resource of type: ocf:heartbeat:CTDB.
It seems to be because the command
<code>
ctdb version
</code>
return Ubuntu in the vesion.

The issue is fixed upstream in the commit https://github.com/ClusterLabs/resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912#diff-6f2dd2a1f5930ef451c54c7bf8df90adc5675aff2e0018552b5f428c66c59060

= To reproduce =

* apt install ctdb pacemaker corosync pcs
* passwd hacluster
* pcs cluster auth localhost -u hacluster
* pcs cluster setup --name test localhost --force --enable
* pcs cluster start --all
* echo "127.0.0.1" > /etc/ctdb/nodes
* touch /etc/default/ctdb
* pcs resource create ctdb ocf:heartbeat:CTDB ctdb_recovery_lock="/tmp/lock"

== Actual result ==
The command
<code>
pcs resource debug-start ctdb
</code>
return
<code>
Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'unknown error' (1)
....

</code>

== Expected result ==

<code>
pcs resource debug-start ctdb
</code>
return
<code>
Operation start for ctdb (ocf:heartbeat:CTDB) returned: 'ok' (0)
....

</code>

description: updated
description: updated
affects: systemd (Ubuntu) → pacemaker (Ubuntu)
description: updated
Revision history for this message
Paride Legovini (paride) wrote :

Thanks David for this bug report. I think this bug belongs to the resource-agents package and not to pacemaker. Please note that resource-agents is in the "universe" component of Ubuntu, and therefore only gets community support. (Ubuntu 21.10 will also offer a resource-agent-supported package offering a subset of the resource-agents with support.)

The fix you pointed to [1] was reverted shortly after being introduced for reasons that are not immediately clear. A larger refactor of those functions was made several versions later in [3], however even should it apply cleanly on Bionic's version proposing it as a SRU fix will require extra care. This is IMHO a starting point for driving the fix forward.

[1] https://github.com/ClusterLabs/resource-agents/commit/0c513d16259d94b492f0fe8dd0cbc2e5f98ee912
[2] https://github.com/ClusterLabs/resource-agents/commit/489afee8c424cf82b398832191bbdf4d06b2e1f2
[3] https://github.com/ClusterLabs/resource-agents/commit/b4df0873bb986524d826a5ba9b24b135cccc0160

affects: pacemaker (Ubuntu) → resource-agents (Ubuntu)
Revision history for this message
David Lechevalier (dlecheva) wrote :

Hi Paride,
Thank you. I didn't know this subtility about resource-agents.

I provided this fix because it is the simple commit to fix the current issue.
What do you mean by "universe" and community support ?
Is there a repository where I can propose something ?

Revision history for this message
Paride Legovini (paride) wrote :

Hi David, on "main" vs "universe" see:

  https://help.ubuntu.com/community/Repositories/Ubuntu

For community help, possibly on driving a Stable Release Upgrade, see:

  https://ubuntu.com/support/community-support

Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

Also please keep in mind that the usage of pcs is still not fully supported by the Ubuntu community, we still recommend crmsh:

https://ubuntu.com/server/docs/ubuntu-ha-introduction

If you want to prepare a package to apply the upstream patch Paride linked I'll be happy to review/sponsor it. For more information on Stable Release Updates (SRU) check the following page:

https://wiki.ubuntu.com/StableReleaseUpdates

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.