Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-63186

Pcs should run crm_verify upon failed 'pcs cluster cib-push' to provide more details [rhel-10]

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • pcs-0.12.0-5.el10
    • None
    • FutureFeature
    • rhel-ha
    • 13
    • 19
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Enhancement
    • Hide
      .`pcs` provides more detailed error messages for failed CIB updates

      Previously, when a CIB update failed when using the `pcs cluster edit` or `pcs cluster cib-push` commands, the error message provided by Pacemaker was generic. It did not explain the specific reason for the failure, which made troubleshooting the invalid configuration difficult.

      With this enhancement, `pcs` is updated to request a detailed validation check from Pacemaker upon a failed CIB push.

      As a result, when a CIB update is rejected, `pcs` now displays a specific error message explaining what is wrong with the configuration.
      Show
      .`pcs` provides more detailed error messages for failed CIB updates Previously, when a CIB update failed when using the `pcs cluster edit` or `pcs cluster cib-push` commands, the error message provided by Pacemaker was generic. It did not explain the specific reason for the failure, which made troubleshooting the invalid configuration difficult. With this enhancement, `pcs` is updated to request a detailed validation check from Pacemaker upon a failed CIB push. As a result, when a CIB update is rejected, `pcs` now displays a specific error message explaining what is wrong with the configuration.
    • Done
    • Done
    • Done
    • Not Required
    • None

      Goal

      As a user, I want to get an explanation of why cib push failed. Currently, pcs only says cib is not valid and dumps the cib.

      Acceptance criteria

      When cib-push fails, pcs runs crm_verify to get a detailed information about the reason of the cib not being accepted by pacemaker. This would only apply to 'pcs cluster cib-push' and 'pcs cluster edit' commands.

      Even though users can run crm_verify on their own, integrating it to pcs cib-push would improve user experience. Also various automation tools running cib-push would benefit from this.

              rhn-support-nhostako Nina Hostakova
              tojeline@redhat.com Tomas Jelinek
              Tomas Jelinek Tomas Jelinek
              Nina Hostakova Nina Hostakova
              Michal Stubna Michal Stubna
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: