RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1286026 - partial_activation check fails in pacemaker
Summary: partial_activation check fails in pacemaker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1269194
TreeView+ depends on / blocked
 
Reported: 2015-11-27 09:38 UTC by Josef Zimek
Modified: 2019-09-12 09:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-02 17:36:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Josef Zimek 2015-11-27 09:38:59 UTC
Description of problem:
=======================
Customer is using a HA-LVM mirror logical volumes as resource for Pacemaker cluster.

When using the option 'partial_activation=true', like in the following resource,

# pcs resource show vgexample
 Resource: vgexample (class=ocf provider=heartbeat type=LVM)
  Attributes: volgrpname=vg_example exclusive=true partial_activation=true
 ...

Customer expects that in case of failure of a logical volume segment (missing PV), the cluster can still activate the VG and start the volume (in the LVM script, 'partial_activation=true' converts to 'vgchange -ay ... <vg> --partial')


But when running:

# pcs resource move res_grp    # res_grp is resource group with the vgexample resource

it fails.


It's because in the LVM ocf script, before doing the vgchange, the script
runs 'vgck <vg>' (in the LVM_validate_all() function) which fails because of
the missing PV.

When commenting out the vgck part as a test and everything worked as expected.





Version-Release number of selected component (if applicable):
=============================================================
RHEL 6.7

# rpm -qf /usr/lib/ocf/resource.d/heartbeat/LVM
resource-agents-3.9.5-24.el6.x86_64



How reproducible:
=================
always


Steps to Reproduce:
===================
1. move resource group which consist of LVM resource with partial_activation=true


Actual results:
===============
Resource group fails to move


Expected results:
=================
The LVM_validate_all() should check the value of OCF_RESKEY_partial_activation
before trying vgck. And the resource group moves to other node


Additional info:

Comment 2 Oyvind Albrigtsen 2015-11-27 09:54:33 UTC
Can he test the patch I've attached to the following bz?
https://bugzilla.redhat.com/show_bug.cgi?id=1266173

Comment 3 Oyvind Albrigtsen 2015-12-16 14:38:33 UTC
Josef: Can you ask the customer if he can test the patch mentioned in comment #2?

Comment 4 Josef Zimek 2015-12-16 15:03:46 UTC
Oyvind: Yes, I will let you know the result once I got feedback from customer. Thanks

Comment 7 John Ruemker 2016-08-02 17:36:26 UTC
Closing this out.  The issue described is resolved via the errata that was released in 6.8 via Bugzilla #1266173.  The customer case eventually closed without confirmation of the fix, but we expect that it should have been resolved.


Note You need to log in before you can comment on or make changes to this bug.