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.
+++ This bug was initially created as a clone of Bug #1644628 +++
In bz1434936, support for validate-all action has been added, allowing pcs to ask fence agents to validate their settings via pacemaker interface. However, the output of validate-all action is unsatisfactory for the intended use in pcs. To fix that, a new validate action is being implemented in fence agents. This new action, validate-all-xml, provides results of validation in xml format (bz1636036).
For pcs to be able to use this, pacemaker should allow to run this new action.
From the pacemaker interface point of view, changing the current interface
stonith_admin --validate --agent AGENT [--quiet] [--option NAME=VALUE] ...
to
stonith_admin --validate-xml --agent AGENT [--quiet] [--option NAME=VALUE] ...
or
stonith_admin --validate --xml --agent AGENT [--quiet] [--option NAME=VALUE] ...
or something similar should do the trick.
On the output side, pacemaker should not mix its own "Validation of AGENT succeeded/failed" message to the xml output from agents.
--- Additional comment from Ken Gaillot on 2018-11-08 16:57:02 EST ---
Considering that there has previously been interest in generating XML output for the --history option as well, I think a separate option makes sense. Maybe --output-format=xml.