Hide Forgot
> Description of problem: Running a 'pcs cluster report' from outside a cluster result in a following error message: [root@virt-153 ~]# pcs cluster report --from "2016-10-25 19:05:28" mylogs Error: virt-153: ERROR: Cannot determine nodes; specify --nodes or --single-node This error is passed directly from crm_report as it suggests using --nodes or --single-node which are however not supported by pcs. So we could either: - mask this specific error to not disclose such options - implement --nodes and --single-node into pcs and pass them as-is to crm_report > Version-Release number of selected component (if applicable): pcs-0.9.154-1.el6.x86_64 Note: the version used here is a RHEL 6 pcs package, but I suppose we're going to leave the fix for RHEL 7.4 / upstream as this is nothing critical.
Created attachment 1321824 [details] proposed fix Before fix: # pcs cluster report /root/report Error: rh74-node3: ERROR: Cannot determine nodes; specify --nodes or --single-node # pcs cluster report /root/report Error: rh74-node1: ERROR: Output directory /root/report already exists, specify an alternate name with --dest After fix: # pcs cluster report /root/report Error: cluster is not configured on this node # pcs cluster report /root/report Error: rh74-node1: ERROR: Output directory /root/report already exists, specify an alternate name with <dest> The error message should now state clearly what the problem is. It was not possible to get a report from outside of a cluster due to pcs not allowing to specify --nodes or --single-node. Once we switch to the new pcs architecture, it will be possible to run commands remotely including this one.
After Fix: [vm-rhel72-1 ~] $ rpm -q pcs pcs-0.9.160-1.el7.x86_64 [vm-rhel72-1 ~] $ mkdir report [vm-rhel72-1 ~] $ pcs cluster report /root/report Error: vm-rhel72-1: Calculated node list: vm-rhel72-1 vm-rhel72-3 vm-rhel72-1: Collecting data from vm-rhel72-1 vm-rhel72-3 (10/09/17 18:00:00 to 10/10/17 18:00:59) vm-rhel72-1: ERROR: Output directory /root/report already exists, specify an alternate name with <dest> [vm-rhel72-1 ~] $ pcs cluster destroy --all vm-rhel72-1: Stopping Cluster (pacemaker)... vm-rhel72-3: Stopping Cluster (pacemaker)... vm-rhel72-1: Successfully destroyed cluster vm-rhel72-3: Successfully destroyed cluster [vm-rhel72-1 ~] $ rm -r report [vm-rhel72-1 ~] $ pcs cluster report /root/report Error: cluster is not configured on this node
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://access.redhat.com/errata/RHBA-2018:0866