Red Hat Bugzilla – Bug 912498
When listing multiple operations pcs should print one per line
Last modified: 2013-11-21 06:51:32 EST
Description of problem: It's difficult to view the operations that are configured for a resource if there is more than one Version-Release number of selected component (if applicable): pcs-0.9.26-10.el6.noarch How reproducible: Always [root@ask-03 ~]# pcs -f test resource create test IPaddr2 [root@ask-03 ~]# pcs -f test resource add_operation IPaddr2 start interval="0" timeout="20s" Unable to find resource: IPaddr2 [root@ask-03 ~]# pcs -f test resource add_operation test start interval="0" timeout="20s" [root@ask-03 ~]# pcs -f test resource add_operation test stop interval="0" timeout="20s" [root@ask-03 ~]# pcs -f test resource add_operation test monitor interval="0" timeout="20s" [root@ask-03 ~]# pcs -f test resource test (ocf::heartbeat:IPaddr2): Stopped [root@ask-03 ~]# pcs -f test resource --all Resource: test (provider=heartbeat type=IPaddr2 class=ocf) Operations: start interval=0 timeout=20s stop interval=0 timeout=20s monitor interval=0 timeout=20s Output should looks something like this: [root@ask-03 ~]# pcs -f test resource --all Resource: test (provider=heartbeat type=IPaddr2 class=ocf) Operations: start interval=0 timeout=20s stop interval=0 timeout=20s monitor interval=0 timeout=20s
Fixed upstream: https://github.com/feist/pcs/commit/9920396944493eff46a58f1855bc9d9eca5e52a4
[root@ask-02 ~]# rpm -q pcs pcs-0.9.64-1.el6.noarch [root@ask-02 ~]# pcs -f test.xml resource create Test Dummy op monitor interval=30s op monitor interval=31s [root@ask-02 ~]# pcs -f test.xml resource show Test Resource: Test (class=ocf provider=heartbeat type=Dummy) Operations: monitor interval=30s (Test-monitor-interval-30s) monitor interval=31s (Test-monitor-interval-31s)
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