Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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-2017:2198
Description of problem: The pcs commands for alert configuration (create and recipient add) are generated without option '-f <file>'. The pcs command for adding recipient (recipient add) has missing named parameter for recipient value 'value=<recipient-value>'. Version-Release number of selected component (if applicable): clufter-cli-0.59.5-2.el7 How reproducible: always Steps to Reproduce: 1. Create cluster with alert configuration: [root@virt-024 ~]# pcs cluster auth virt-0{24,27} virt-024: Already authorized virt-027: Already authorized [root@virt-024 ~]# pcs cluster setup --start --name cluster virt-0{24,27} Destroying cluster on nodes: virt-024, virt-027... virt-024: Stopping Cluster (pacemaker)... virt-027: Stopping Cluster (pacemaker)... virt-024: Successfully destroyed cluster virt-027: Successfully destroyed cluster Sending cluster config files to the nodes... virt-024: Succeeded virt-027: Succeeded Starting cluster on nodes: virt-024, virt-027... virt-024: Starting Cluster... virt-027: Starting Cluster... Synchronizing pcsd certificates on nodes virt-024, virt-027... virt-024: Success virt-027: Success Restarting pcsd on the nodes in order to reload the certificates... virt-024: Success virt-027: Success [root@virt-024 ~]# pcs stonith create fence-virt-024 fence_xvm params pcmk_host_check="static-list" pcmk_host_list="virt-024" pcmk_host_map="virt-024:virt-024.cluster-qe.lab.eng.brq.redhat.com" Setting fence-virt-024 on virt-024.cluster-qe.lab.eng.brq.redhat.com [root@virt-024 ~]# pcs stonith create fence-virt-027 fence_xvm params pcmk_host_check="static-list" pcmk_host_list="virt-027" pcmk_host_map="virt-027:virt-027.cluster-qe.lab.eng.brq.redhat.com" Setting fence-virt-027 on virt-027.cluster-qe.lab.eng.brq.redhat.com [root@virt-024 ~]# pcs alert create path=/path/to/file id=alert-1 [root@virt-024 ~]# pcs alert recipient add alert-1 value=recipient id=recipient-1 2. Generate pcs commads by clufter for current cluster configuration: [root@virt-024 ~]# clufter pcs2pcscmd --batch --quiet --silent --text-width=-1 # sequence generated on 2016-10-04 12:49:02 with: clufter 0.59.5 # invoked as: ['/usr/bin/clufter', 'pcs2pcscmd', '--batch', '--quiet', '--silent', '--text-width=-1'] # targeting system: ('linux', 'redhat', '7.3', 'Maipo') pcs cluster auth virt-024 virt-027 for l in $( comm -12 \ <( python -m json.tool /var/lib/pcsd/pcs_users.conf | sed -n 's|^\s*"[^"]\+":\s*"\([0-9a-f-]\+\)".*|\1|1p' | sort ) \ <( python -m json.tool /var/lib/pcsd/tokens | sed -n 's|^\s*"[^"]\+":\s*"\([0-9a-f-]\+\)".*|\1|1p' | sort ) ) @SENTINEL@ ; do grep -Eq \ "$( python -m json.tool /var/lib/pcsd/tokens | sed -n "s|^\s*\"\([^\"]\+\)\":\s*\"${l}\".*|\1|1p" )" - <<<' virt-024 virt-027' && break ; false ; done || { echo 'WARNING: cluster being created ought to include this very local machine' \ ; read -p 'Do you want to continue [yN] (60s timeout): ' -t 60 || : ; test "${REPLY}" = y || kill -INT "$$" ; } pcs cluster setup --name cluster virt-024 virt-027 --transport udpu pcs cluster start --all --wait=60 pcs cluster cib tmp-cib.xml pcs -f tmp-cib.xml stonith create fence-virt-024 fence_xvm pcmk_host_check=static-list pcmk_host_list=virt-024 pcmk_host_map=virt-024:virt-024.cluster-qe.lab.eng.brq.redhat.com op monitor id=fence-virt-024-monitor-interval-60s interval=60s name=monitor pcs -f tmp-cib.xml stonith create fence-virt-027 fence_xvm pcmk_host_check=static-list pcmk_host_list=virt-027 pcmk_host_map=virt-027:virt-027.cluster-qe.lab.eng.brq.redhat.com op monitor id=fence-virt-027-monitor-interval-60s interval=60s name=monitor pcs alert create path=/path/to/file id=alert-1 pcs alert recipient add alert-1 recipient id=recipient-1 pcs cluster cib-push tmp-cib.xml --config Actual results: pcs alert create path=/path/to/file id=alert-1 pcs alert recipient add alert-1 recipient id=recipient-1 Expected results: pcs -f tmp-cib.xml alert create path=/path/to/file id=alert-1 pcs -f tmp-cib.xml alert recipient add alert-1 value=recipient id=recipient-1 Additional info: