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 1176687 - Pacemaker resource defaults should show up in 'pcs config' output
Summary: Pacemaker resource defaults should show up in 'pcs config' output
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks: 1187488 1205796
TreeView+ depends on / blocked
 
Reported: 2014-12-22 20:14 UTC by Chris Feist
Modified: 2015-11-19 09:34 UTC (History)
3 users (show)

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.
Clone Of:
: 1187488 (view as bug list)
Environment:
Last Closed: 2015-11-19 09:34:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (10.48 KB, patch)
2015-01-30 09:21 UTC, Tomas Jelinek 		no flags Details | Diff
proposed fix (10.69 KB, patch)
2015-01-30 09:39 UTC, Tomas Jelinek 		no flags Details | Diff
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2290 0 normal SHIPPED_LIVE Moderate: pcs security, bug fix, and enhancement update 2015-11-19 09:43:53 UTC

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
Note You need to log in before you can comment on or make changes to this bug.