Bug 1187488
| Summary: | Pacemaker resource defaults should show up in 'pcs config' output | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Tomas Jelinek <tojeline> |
| Component: | pcs | Assignee: | Tomas Jelinek <tojeline> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.6 | CC: | cfeist, cluster-maint, cluster-qe, rsteiger, tojeline |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcs-0.9.139-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
* The "pcs status --full" command did not output the node attributes and migration summary. Similarly, the "pcs config" command did not display the resource and operation defaults. Both commands have been modified to display this information. (BZ#1184922, BZ#1187488)
|
Story Points: | --- |
| Clone Of: | 1176687 | Environment: | |
| Last Closed: | 2015-07-22 06:16:09 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: | 1176687 | ||
| Bug Blocks: | |||
|
Description
Tomas Jelinek
2015-01-30 08:22:40 UTC
Upstream patch: https://github.com/feist/pcs/commit/ac492e40ef855b0a013e21926314bde5e2793aeb Test: [root@rh66-node1:~]# pcs resource defaults No defaults set [root@rh66-node1:~]# pcs resource defaults resource-stickines=500 [root@rh66-node1:~]# pcs resource defaults resource-stickines: 500 [root@rh66-node1:~]# pcs config | grep resource-stickines resource-stickines: 500 [root@rh66-node1:~]# pcs resource op defaults No defaults set [root@rh66-node1:~]# pcs resource op defaults timeout=30 [root@rh66-node1:~]# pcs resource op defaults timeout: 30 [root@rh66-node1:~]# pcs config | grep 'timeout:' timeout: 30 Before Fix:
[root@rh66-node1 ~]# rpm -q pcs
pcs-0.9.138-1.el6.x86_64
[root@rh66-node1:~]# pcs config
Cluster Name: cluster66
Corosync Nodes:
rh66-node1 rh66-node2
Pacemaker Nodes:
rh66-node1 rh66-node2
Resources:
Stonith Devices:
Fencing Levels:
Location Constraints:
Ordering Constraints:
Colocation Constraints:
Cluster Properties:
cluster-infrastructure: cman
dc-version: 1.1.11-97629de
last-lrm-refresh: 1417169339
[root@rh66-node1:~]# pcs resource defaults resource-stickines=500
[root@rh66-node1:~]# pcs resource op defaults timeout=30
[root@rh66-node1:~]# pcs config
Cluster Name: cluster66
Corosync Nodes:
rh66-node1 rh66-node2
Pacemaker Nodes:
rh66-node1 rh66-node2
Resources:
Stonith Devices:
Fencing Levels:
Location Constraints:
Ordering Constraints:
Colocation Constraints:
Cluster Properties:
cluster-infrastructure: cman
dc-version: 1.1.11-97629de
last-lrm-refresh: 1417169339
After Fix:
[root@rh66-node1:~]# rpm -q pcs
pcs-0.9.139-1.el6.x86_64
[root@rh66-node1:~]# pcs config
Cluster Name: cluster66
{snip}
Colocation Constraints:
Resources Defaults:
No defaults set
Operations Defaults:
No defaults set
Cluster Properties:
cluster-infrastructure: cman
dc-version: 1.1.11-97629de
last-lrm-refresh: 1417169339
[root@rh66-node1:~]# pcs resource defaults resource-stickines=500
[root@rh66-node1:~]# pcs resource op defaults timeout=30
[root@rh66-node1:~]# pcs config
Cluster Name: cluster66
{snip}
Colocation Constraints:
Resources Defaults:
resource-stickines: 500
Operations Defaults:
timeout: 30
Cluster Properties:
cluster-infrastructure: cman
dc-version: 1.1.11-97629de
last-lrm-refresh: 1417169339
[root@rh66-node1:~]# pcs resource defaults resource-stickines=
[root@rh66-node1:~]# pcs resource op defaults timeout=
[root@rh66-node1:~]# pcs config
Cluster Name: cluster66
{snip}
Colocation Constraints:
Resources Defaults:
No defaults set
Operations Defaults:
No defaults set
Cluster Properties:
cluster-infrastructure: cman
dc-version: 1.1.11-97629de
last-lrm-refresh: 1417169339
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-1446.html |