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 1643306 - LVM-activate: lvmlockd_check needs $OCF_ERR_GENERIC instead of $OCF_ERR_CONFIGURED
Summary: LVM-activate: lvmlockd_check needs $OCF_ERR_GENERIC instead of $OCF_ERR_CONFI...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1643307
TreeView+ depends on / blocked
 
Reported: 2018-10-25 21:48 UTC by Corey Marthaler
Modified: 2019-08-06 12:02 UTC (History)
7 users (show)

Fixed In Version: resource-agents-4.1.1-15.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1643307 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:01:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3779121 0 None None None 2018-12-29 05:59:35 UTC
Red Hat Product Errata RHBA-2019:2012 0 None None None 2019-08-06 12:02:01 UTC

Description Corey Marthaler 2018-10-25 21:48:49 UTC 
Description of problem:
The current lvmlockd_check during initial start up can fail, causing configuration issues for resources dependent on it. 

Oct 25 15:31:12 harding-03 LVM-activate(sharedlv1)[34495]: ERROR: lvmlockd daemon is not running!
Oct 25 15:31:12 harding-03 LVM-activate(sharedlv2)[34498]: ERROR: lvmlockd daemon is not running!
Oct 25 15:31:12 harding-03 LVM-activate(sharedlv3)[34564]: ERROR: lvmlockd daemon is not running!
Oct 25 15:31:12 harding-03 lrmd[34334]:  notice: sharedlv1_monitor_0:34495:stderr [ ocf-exit-reason:lvmlockd daemon is not running! ]
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: Result of probe operation for sharedlv1 on harding-03: 6 (not configured)
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: harding-03-sharedlv1_monitor_0:20 [ ocf-exit-reason:lvmlockd daemon is not running!\n ]
Oct 25 15:31:12 harding-03 lrmd[34334]:  notice: sharedlv2_monitor_0:34498:stderr [ ocf-exit-reason:lvmlockd daemon is not running! ]
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: Result of probe operation for sharedlv2 on harding-03: 6 (not configured)
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: harding-03-sharedlv2_monitor_0:25 [ ocf-exit-reason:lvmlockd daemon is not running!\n ]
Oct 25 15:31:12 harding-03 crmd[34337]: warning: Action 14 (sharedlv1:0_monitor_0) on harding-03 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: Transition aborted by operation sharedlv1_monitor_0 'modify' on harding-03: Event failed
Oct 25 15:31:12 harding-03 lrmd[34334]:  notice: sharedlv3_monitor_0:34564:stderr [ ocf-exit-reason:lvmlockd daemon is not running! ]
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: Result of probe operation for sharedlv3 on harding-03: 6 (not configured)
Oct 25 15:31:12 harding-03 crmd[34337]:  notice: harding-03-sharedlv3_monitor_0:40 [ ocf-exit-reason:lvmlockd daemon is not running!\n ]
Oct 25 15:31:12 harding-03 crmd[34337]: warning: Action 15 (sharedlv2:0_monitor_0) on harding-03 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:12 harding-03 crmd[34337]: warning: Action 18 (sharedlv3:0_monitor_0) on harding-03 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:13 harding-03 crmd[34337]: warning: Action 5 (sharedlv1:1_monitor_0) on harding-02 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:13 harding-03 crmd[34337]: warning: Action 6 (sharedlv2:1_monitor_0) on harding-02 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:13 harding-03 crmd[34337]: warning: Action 9 (sharedlv3:1_monitor_0) on harding-02 failed (target: 7 vs. rc: 6): Error
Oct 25 15:31:13 harding-03 crmd[34337]:  notice: Transition 0 (Complete=21, Pending=0, Fired=0, Skipped=3, Incomplete=49, Source=/var/lib/pacemaker/pengine/pe-input-572.bz2): Stopped
Oct 25 15:31:13 harding-03 pengine[34336]: warning: Processing failed probe of sharedlv1:0 on harding-03: not configured
Oct 25 15:31:13 harding-03 pengine[34336]:  notice: If it is not possible for sharedlv1:0 to run on harding-03, see the resource-discovery option for location constraints
Oct 25 15:31:13 harding-03 pengine[34336]:   error: Preventing shared_vg1-clone from re-starting anywhere: operation monitor failed 'not configured' (6)
Oct 25 15:31:13 harding-03 pengine[34336]: warning: Processing failed probe of sharedlv1:0 on harding-03: not configured
Oct 25 15:31:13 harding-03 pengine[34336]:  notice: If it is not possible for sharedlv1:0 to run on harding-03, see the resource-discovery option for location constraints
Oct 25 15:31:13 harding-03 pengine[34336]:   error: Preventing shared_vg1-clone from re-starting anywhere: operation monitor failed 'not configured' (6)
Oct 25 15:31:13 harding-03 pengine[34336]: warning: Processing failed probe of sharedlv2:0 on harding-03: not configured
Oct 25 15:31:13 harding-03 pengine[34336]:  notice: If it is not possible for sharedlv2:0 to run on harding-03, see the resource-discovery option for location constraints
Oct 25 15:31:13 harding-03 pengine[34336]:   error: Preventing shared_vg1-clone from re-starting anywhere: operation monitor failed 'not configured' (6)


Version-Release number of selected component (if applicable):
resource-agents-4.1.1-12.el7.x86_64
Comment 4 Oyvind Albrigtsen 2019-01-09 15:53:41 UTC 
https://github.com/ClusterLabs/resource-agents/pull/1281
Comment 8 errata-xmlrpc 2019-08-06 12:01:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2012
Note You need to log in before you can comment on or make changes to this bug.