Bug 1176687

Summary: Pacemaker resource defaults should show up in 'pcs config' output
Product: Red Hat Enterprise Linux 7 Reporter: Chris Feist <cfeist>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact: Steven J. Levine <slevine>
Priority: medium    
Version: 7.1CC: cluster-maint, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.140-1.el7 Doc Type: Bug Fix
Doc Text:
Cause: User runs 'pcs config' to get complete cluster configuration. Consequence: Resource defaults and operations defaults missing in the output. Fix: Add resources defaults and operations defaults to 'pcs config' output. Result: Resources defaults and operations defaults are present in 'pcs config' output.
Story Points: ---
Clone Of:
: 1187488 (view as bug list) Environment:
Last Closed: 2015-11-19 09:34:00 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:
Bug Depends On:    
Bug Blocks: 1187488, 1205796    
Attachments:
Description Flags
proposed fix
none
proposed fix none

Description Chris Feist 2014-12-22 20:14:47 UTC
Description of problem:
pacemaker resource defaults are not shown in 'pcs config' output

Version-Release number of selected component (if applicable):
pcs-0.9.137-5.el7.x86_64

How reproducible:


Steps to Reproduce:
[root@rh7-1 ~]# pcs resource defaults 
No defaults set
[root@rh7-1 ~]# pcs resource defaults resource-stickiness=500
[root@rh7-1 ~]# pcs resource defaults     
resource-stickiness: 500
[root@rh7-1 ~]# pcs config | grep resource-stickiness
[root@rh7-1 ~]# 


pcs config output should show resource defaults

Comment 1 Tomas Jelinek 2015-01-30 09:21:00 UTC
Created attachment 985904 [details]
proposed fix

Test:

[root@rh70-node1:~]# pcs resource defaults
No defaults set
[root@rh70-node1:~]# pcs resource defaults resource-stickines=500
[root@rh70-node1:~]# pcs resource defaults
resource-stickines: 500
[root@rh70-node1:~]# pcs config | grep resource-stickines
 resource-stickines: 500

Comment 2 Tomas Jelinek 2015-01-30 09:39:13 UTC
Created attachment 985907 [details]
proposed fix

Test:

[root@rh70-node1:~]# pcs resource defaults
No defaults set
[root@rh70-node1:~]# pcs resource defaults resource-stickines=500
[root@rh70-node1:~]# pcs resource defaults
resource-stickines: 500
[root@rh70-node1:~]# pcs config | grep resource-stickines
 resource-stickines: 500

[root@rh70-node1:~]# pcs resource op defaults
No defaults set
[root@rh70-node1:~]# pcs resource op defaults timeout=30
[root@rh70-node1:~]# pcs resource op defaults
timeout: 30
[root@rh70-node1:~]# pcs config | grep 'timeout:'
 timeout: 30

Comment 4 Tomas Jelinek 2015-06-04 14:35:08 UTC
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64
[root@rh70-node1:~]# pcs resource defaults
No defaults set
[root@rh70-node1:~]# pcs resource defaults resource-stickines=500
[root@rh70-node1:~]# pcs resource defaults
resource-stickines: 500
[root@rh70-node1:~]# pcs config | grep resource-stickines
[root@rh70-node1:~]# pcs resource op defaults
No defaults set
[root@rh70-node1:~]# pcs resource op defaults timeout=30
[root@rh70-node1:~]# pcs resource op defaults
timeout: 30
[root@rh70-node1:~]# pcs config | grep 'timeout:'



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el6.x86_64
[root@rh70-node1:~]# pcs resource defaults
No defaults set
[root@rh70-node1:~]# pcs resource defaults resource-stickines=500
[root@rh70-node1:~]# pcs resource defaults
resource-stickines: 500
[root@rh70-node1:~]# pcs config | grep resource-stickines
 resource-stickines: 500
[root@rh70-node1:~]# pcs resource op defaults
No defaults set
[root@rh70-node1:~]# pcs resource op defaults timeout=30
[root@rh70-node1:~]# pcs resource op defaults
timeout: 30
[root@rh70-node1:~]# pcs config | grep 'timeout:'
 timeout: 30

Comment 8 errata-xmlrpc 2015-11-19 09:34:00 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/RHSA-2015-2290.html