Bug 912496

Summary: Allow multiple 'op' options when creating a resource
Product: Red Hat Enterprise Linux 6 Reporter: Chris Feist <cfeist>
Component: pcsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: cluster-maint, fdanapfe, jkortus, lnovich, rsteiger, slevine
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: pcs-0.9.64-1.el6 Doc Type: Bug Fix
Doc Text:
Cause: Multiple resource operations could not be specified when creating a resource Consequence: Only resources with one operation could be created Fix: 'pcs resource create' was updated to allow multiple operations to be created with a resource Result: Users can now create resources with multiple operations
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 11:51:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chris Feist 2013-02-18 20:03:15 UTC
Description of problem:
Currently it isn't possible to specify multiple 'op' options when creating a resource with pcs.

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

How reproducible:

Steps to Reproduce:
1. pcs resource create test_res IPaddr2 ip="" op start interval="0" timeout="20s" op stop interval="0" timeout="20s"
Actual results:
Only one operation is created

Expected results:
Both operations are created

Comment 8 Chris Feist 2013-08-13 21:33:58 UTC

*** This bug has been marked as a duplicate of bug 902451 ***

Comment 10 Chris Feist 2013-08-13 23:44:06 UTC
*** Bug 902451 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2013-11-21 11:51:24 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.