Hide Forgot
Description of problem: pcs update resource with operation does not work as expected. Instead of updating the operation, the parameters are added to the resource. Version-Release number of selected component (if applicable): pcs-0.9.26-9.el6.noarch How reproducible: always Steps to Reproduce: 1. pcs resource create dummystateful ocf:pacemaker:Stateful op monitor interval="30s" 2. pcs resource update dummystateful op monitor interval="19s" 3. Actual results: $ pcs resource show dummystateful Resource: dummystateful interval: 19s op monitor interval=30s Expected results: $ pcs resource show dummystateful Resource: dummystateful op monitor interval=19s Additional info:
Fixed upstream: https://github.com/feist/pcs/commit/6a95a470e6811be0e7ff7ca5eb9be88aeb9f3c74 https://github.com/feist/pcs/commit/0a50beea8a327c1eb8b02a0af6fc9821b4b330e6 This replaces the first monitor/start/stop/etc. operation that is found for the specified resource (or if no such operation is found it creates a new one).
Are there any plans to get this fixed in RHEL 6.4?
That's very unlikely as pacemaker is still techpreview in 6.4 (AFAIK).
Cross-filed case 00902474 on the Red Hat customer portal.
Feedback: We applied the patches from comment #2 to pcs-0.9.26-10.el6_4.1 and it now works as expected.
[root@ask-02 ~]# pcs -f test.xml resource create dummystateful ocf:pacemaker:Stateful op monitor interval="30s" [root@ask-02 ~]# pcs -f test.xml rseource update dummystateful op monitor interval=19s [root@ask-02 ~]# pcs -f test.xml resource --full Resource: dummystateful (class=ocf provider=pacemaker type=Stateful) Operations: monitor interval=19s (dummystateful-monitor-interval-19s) [root@ask-02 ~]# pcs -f test.xml resource update dummystateful op monitor interval=29s [root@ask-02 ~]# pcs -f test.xml resource --full Resource: dummystateful (class=ocf provider=pacemaker type=Stateful) Operations: monitor interval=29s (dummystateful-monitor-interval-29s) [root@ask-02 ~]#
It still doesn't works with pcs-0.9.26-10.el6_4.1 :s
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. http://rhn.redhat.com/errata/RHBA-2013-1633.html