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 1171162 - clvmd resource does not parse daemon_options correctly
Summary: clvmd resource does not parse daemon_options correctly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Fabio Massimo Di Nitto
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-05 15:23 UTC by Nenad Peric
Modified: 2015-11-19 04:41 UTC (History)
3 users (show)

Fixed In Version: resource-agents-3.9.5-45.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 04:41:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2190 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2015-11-19 08:06:48 UTC

Description Nenad Peric 2014-12-05 15:23:26 UTC
Description of problem:

If you define an additional daemon_options for clvmd, the options are ignored when the resource is started. 

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

resource-agents-3.9.5-38.el7.x86_64

How reproducible:

Everytime

Steps to Reproduce:

1. pcs resource update clvmd daemon_options=-d2
2. restart the cluster


Actual results:

the clvmd is started without the daemon_options

Expected results:

clvmd to start with any options additionally provided.

Additional info:

could be fixed by editing line 303 of 
/usr/lib/ocf/resource.d/heartbeat/clvm:

local opts="${@:2}"

(currently it reads only $2)

Comment 1 David Vossel 2014-12-05 15:40:49 UTC
putting quotes here around the 2nd arg would fix this as well.

https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/clvm#L363

Comment 2 David Vossel 2015-04-29 15:18:46 UTC
patch posted.
https://github.com/ClusterLabs/resource-agents/pull/606

Comment 4 michal novacek 2015-08-12 15:02:47 UTC
I have verified with clvmd in resource-agents-3.9.5-50.el7.x86_64 that
paramaters supplied with daemon_options parameter are correctly used when
starting the daemon.

---

[root@virt-151 ~]# pcs resource show clvmd
 Resource: clvmd (class=ocf provider=heartbeat type=clvm)
  Attributes: with_cmirrord=1
  Operations: start interval=0s timeout=90 (clvmd-start-timeout-90)
              stop interval=0s timeout=90 (clvmd-stop-timeout-90)
              monitor interval=30s on-fail=fence (clvmd-monitor-interval-30s)

[root@virt-151 ~]# ps axf | grep clvmd
14407 pts/0    S+     0:00          \_ grep --color=auto clvmd
 7746 ?        SLsl   0:00 /usr/sbin/clvmd -T90 -d0

BEFORE THE FIX (resource-agents-3.9.5-30.el7.x86_64)
---------------------------------------------------

[root@virt-151 ~]# pcs resource disable clvmd
[root@virt-151 ~]# pcs resource update clvmd daemon_options=-d2
[root@virt-151 ~]# pcs resource enable clvmd

[root@virt-151 ~]# pcs resource show clvmd
 Resource: clvmd (class=ocf provider=heartbeat type=clvm)
  Attributes: with_cmirrord=1 daemon_options=-d2
  Operations: start interval=0s timeout=90 (clvmd-start-timeout-90)
              stop interval=0s timeout=90 (clvmd-stop-timeout-90)
              monitor interval=30s on-fail=fence (clvmd-monitor-interval-30s)

[root@virt-151 ~]# ps axf | grep clvmd
14407 pts/0    S+     0:00          \_ grep --color=auto clvmd
 7746 ?        SLsl   0:00 /usr/sbin/clvmd -T90


AFTER THE FIX (resource-agents-3.9.5-50.el7.x86_64)
---------------------------------------------------

[root@virt-151 ~]# pcs resource disable clvmd
[root@virt-151 ~]# pcs resource update clvmd daemon_options=-d2
[root@virt-151 ~]# pcs resource enable clvmd

[root@virt-151 ~]# pcs resource show clvmd
 Resource: clvmd (class=ocf provider=heartbeat type=clvm)
  Attributes: with_cmirrord=1 daemon_options=-d2
  Operations: start interval=0s timeout=90 (clvmd-start-timeout-90)
              stop interval=0s timeout=90 (clvmd-stop-timeout-90)
              monitor interval=30s on-fail=fence (clvmd-monitor-interval-30s)

[root@virt-151 ~]# ps axf | grep clvmd
14407 pts/0    S+     0:00          \_ grep --color=auto clvmd
 7746 ?        SLsl   0:00 /usr/sbin/clvmd -T90 -d2

Comment 7 errata-xmlrpc 2015-11-19 04:41:06 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://rhn.redhat.com/errata/RHBA-2015-2190.html


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