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 912498 - When listing multiple operations pcs should print one per line
Summary: When listing multiple operations pcs should print one per line
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcs
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-18 20:07 UTC by Chris Feist
Modified: 2013-11-21 11:51 UTC (History)
6 users (show)

Fixed In Version: pcs-0.9.64-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: When a resource had multiple operations they were all displayed on the same line. Consequence: It could be difficult to see all operations a particular resource had Fix: Each resource operation is now displayed on it's own line. Result: It's easier to view resources with multiple operations.
Clone Of:
Environment:
Last Closed: 2013-11-21 11:51:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1633 0 normal SHIPPED_LIVE pcs bug fix and enhancement update 2013-11-20 21:53:48 UTC

Description Chris Feist 2013-02-18 20:07:44 UTC 
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
Comment 2 Chris Feist 2013-03-07 20:56:23 UTC 
Fixed upstream:
https://github.com/feist/pcs/commit/9920396944493eff46a58f1855bc9d9eca5e52a4
Comment 8 Chris Feist 2013-08-13 21:21:02 UTC 
[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)
Comment 11 errata-xmlrpc 2013-11-21 11:51:32 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.

http://rhn.redhat.com/errata/RHBA-2013-1633.html
Note You need to log in before you can comment on or make changes to this bug.