Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1099077

Summary: resource update on a clone ID returns error
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: cfeist, cluster-maint, mjuricek, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.126-1.el7 Doc Type: Bug Fix
Doc Text:
Cause: Pcs use the same code for clone creation and clone update. This code checks for clone existence and exits with an error if clone already exists. Consequence: It is not possible to update clone resource using 'pcs resource update' command. Fix: Condition has been changed so in case of clone update the clone is allowed and need to exists. Result: It is possible to update clone resources using pcs.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 09:19:31 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:
Embargoed:
Attachments:
Description Flags
proposed fix
none
proposed code deduplication
none
proposed fix for group clones none

Description Tomas Jelinek 2014-05-19 12:51:23 UTC 
Description of problem:
Trying to do resource update on a clone ID will return "Error: <resource> is already a clone resource"

Version-Release number of selected component (if applicable):
pcs-0.9.115-32.el7

How reproducible:
always

Steps to Reproduce:
1. Create clone resource, e.g. 'pcs resource clone dummy1'
2. Run 'pcs resource update' on a clone resource

Actual results:
Resource is not updated and error message is presented to the user.
[root@localhost pcs]# pcs resource update dummy1-clone fake=foo
Error: dummy1 is already a clone resource

Expected results:
Update resource without error messages.
Comment 2 Tomas Jelinek 2014-05-20 13:00:36 UTC 
Created attachment 897569 [details]
proposed fix
Comment 3 Tomas Jelinek 2014-05-20 13:01:03 UTC 
Created attachment 897570 [details]
proposed code deduplication
Comment 4 Tomas Jelinek 2014-05-20 13:24:46 UTC 
Created attachment 897573 [details]
proposed fix for group clones
Comment 5 Tomas Jelinek 2014-09-11 09:05:53 UTC 
Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.115-32.el7.x86_64
[root@rh70-node1 ~]# pcs resource create dummy Dummy --clone
[root@rh70-node1 ~]# pcs resource update dummy-clone fake=foo
Error: dummy is already a clone resource
[root@rh70-node1 ~]# echo $?
1

After Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.126-1.el7.x86_64
[root@rh70-node1 ~]# pcs resource create dummy Dummy --clone
[root@rh70-node1 ~]# pcs resource update dummy-clone fake=foo
[root@rh70-node1 ~]# echo $?
0
[root@rh70-node1 ~]# pcs resource --full
 Clone: dummy-clone
  Meta Attrs: fake=foo 
  Resource: dummy (class=ocf provider=heartbeat type=Dummy)
   Operations: start interval=0s timeout=20 (dummy-start-timeout-20)
               stop interval=0s timeout=20 (dummy-stop-timeout-20)
               monitor interval=10 timeout=20 (dummy-monitor-interval-10)
Comment 9 errata-xmlrpc 2015-03-05 09:19:31 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-0415.html
Comment 10 Chris Feist 2015-03-26 20:44:04 UTC 
*** Bug 1198371 has been marked as a duplicate of this bug. ***