Why does the start operation of a `LVM-activate` resource reports success even if the VG failed to be activated?

Solution Verified - Updated -

Issue

  • During the start operation of a LVM-activate resource, Pacemaker reports success (ok) while the activation of the VG reports an error:

    pacemaker-controld[1348]: notice: Initiating start operation shared-lvm-resource_start_0 locally on fastvm-rhel-8-9-201
    pacemaker-controld[1348]: notice: Initiating start operation shared-lvm-resource:1_start_0 on fastvm-rhel-8-9-202
    pacemaker-controld[1348]: notice: Requesting local execution of start operation for shared-lvm-resource on fastvm-rhel-8-9-201
    ...
    LVM-activate(shared-lvm-resource)[3682]: INFO: Activating vg_shared/lv_ha
    ...
    LVM-activate(shared-lvm-resource)[3706]: INFO:  VG vg_shared starting dlm lockspace Starting locking. Waiting until locks are ready...
    LVM-activate(shared-lvm-resource)[3718]: ERROR: vg_shared/lv_ha: failed to activate.
    pacemaker-controld[1348]: notice: Result of start operation for shared-lvm-resource on fastvm-rhel-8-9-201: ok
    
  • This results in a recovery loop (stop/start) because the monitor operation reports an unexpected error; the stop operation is executed successfully but the subsequent start operation fails again and the loop starts again:

    pacemaker-schedulerd[1347]: warning: Unexpected result (error) was recorded for monitor of shared-lvm-resource:1 on fastvm-rhel-8-9-202 at Jun  3 14:16:42 2024
    pacemaker-schedulerd[1347]: notice: Actions: Recover    shared-lvm-resource:1         ( fastvm-rhel-8-9-202 )
    ...
    pacemaker-controld[1348]: notice: Requesting local execution of stop operation for shared-lvm-resource on fastvm-rhel-8-9-201
    LVM-activate(shared-lvm-resource)[3737]: INFO: vg_shared/lv_ha: has already been deactivated.
    pacemaker-controld[1348]: notice: Result of stop operation for shared-lvm-resource on fastvm-rhel-8-9-201: ok
    pacemaker-controld[1348]: notice: Initiating start operation shared-lvm-resource_start_0 locally on fastvm-rhel-8-9-201
    pacemaker-controld[1348]: notice: Initiating start operation shared-lvm-resource_start_0 on fastvm-rhel-8-9-202
    pacemaker-controld[1348]: notice: Requesting local execution of start operation for shared-lvm-resource on fastvm-rhel-8-9-201
    LVM-activate(shared-lvm-resource)[3802]: INFO: Activating vg_shared/lv_ha
    LVM-activate(shared-lvm-resource)[3813]: INFO:  Starting locking. Waiting until locks are ready...
    LVM-activate(shared-lvm-resource)[3825]: ERROR: vg_shared/lv_ha: failed to activate.
    pacemaker-controld[1348]: notice: Result of start operation for shared-lvm-resource on fastvm-rhel-8-9-201: ok
    

Environment

Red Hat Enterprise Linux 8 with Resilient Storage Add-On
Pacemaker cluster with shared storage in Active/Active mode with lvmlockd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content