Hide Forgot
# pcs cluster status > Cluster Status: > Stack: corosync > Current DC: virt-123 (version 1.1.15-10.el7-e174ec8) - partition with quorum > Last updated: Wed Dec 7 10:52:16 2016 Last change: Fri Nov 25 17:17:31 2016 by root via cibadmin on virt-127 > 6 nodes and 6 resources configured ^^^^^^^^^^^ > > PCSD Status: > virt-127: Online > virt-129: Online > virt-130: Online > virt-123: Online > virt-128: Online > virt-131: Online # pcs resource > NO resources configured ^^^^^^^^^^^^
The point here is that configured fence agent instances counts into the total sum of resources in case of "pcs cluster status": # pcs stonith > fence-virt-127 (stonith:fence_xvm): Started virt-123 > fence-virt-123 (stonith:fence_xvm): Started virt-127 > fence-virt-130 (stonith:fence_xvm): Started virt-128 > fence-virt-131 (stonith:fence_xvm): Started virt-129 > fence-virt-129 (stonith:fence_xvm): Started virt-130 > fence-virt-128 (stonith:fence_xvm): Started virt-131 Note also the inconsistency in the leading spaces: * pcs cluster status: - one space under "Cluster Status" header - two spaces under "PCSD Status" header * pcs stonith: - one space (without any header)
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.