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

[RFE] Warn if users action could lead to cluster without fencing [rhel-9]

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • pcs-0.11.9-3.el9
    • None
    • FutureFeature
    • rhel-ha
    • 13
    • 23
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Feature
    • Hide
      .`pcs` warns users before removing the last fencing device

      Before this update, `pcs` allowed users to disable or remove the last fencing device from a cluster without a warning. This could inadvertently leave the cluster in an unsupported state without any STONITH or SBD fencing configured.

      With this enhancement, `pcs` now includes a safety check to prevent the accidental removal of all fencing mechanisms.

      As a result, if you attempt an action that would leave the cluster without any fencing, `pcs` displays an error and blocks the change by default. For example, this occurs when you try to remove the last STONITH resource while SBD is disabled. You can override this safety check to force the change if needed.
      Show
      .`pcs` warns users before removing the last fencing device Before this update, `pcs` allowed users to disable or remove the last fencing device from a cluster without a warning. This could inadvertently leave the cluster in an unsupported state without any STONITH or SBD fencing configured. With this enhancement, `pcs` now includes a safety check to prevent the accidental removal of all fencing mechanisms. As a result, if you attempt an action that would leave the cluster without any fencing, `pcs` displays an error and blocks the change by default. For example, this occurs when you try to remove the last STONITH resource while SBD is disabled. You can override this safety check to force the change if needed.
    • Done
    • Done
    • Done
    • Not Required
    • None

      This is a clone of issue RHEL-66607 to use for version rhel-9.7
      –
      Original description:

      Goal

      The cluster will lose fencing, when a user runs e.g. `pcs stonith sbd disable` and no other fencing mechanism is configured. The user should be warned about this.

      Please, check if fencing will be lost after actions that can lead to it. Send forceable error if such situation can happen.

      This issue can be complex (it is necessary to check sbd and also fence device commands). So, this problem could be solved by planning and creating separate JIRAs for each subtask.

      Acceptance criteria

      • pcs exits with an error and doesn't change cluster configuration in these scenarios:
        • user disables sbd (using 'pcs stonith sbd disable' command) and there are no effective stonith resources in the cluster
        • user disables the last effective stonith resource in the cluster (using 'pcs stonith disable' command) and sbd is disabled
        • user disables a group or a clone or a cloned group containing the last effective stonith resource in the cluster and sbd is disabled
        • user removes the last effective stonith resource in the cluster (using 'pcs stonith delete | remove' command) and sbd is disabled
        • user removes a group or a clone or a cloned group containing the last effective stonith resource in the cluster and sbd is disabled
      • web ui reports an error and doesn't change cluster configuration in the same scenarios:
        • user disables sbd (using 'Disable SBD' button) and there are no effective stonith resources in the cluster
        • user removes the last effective stonith resource in the cluster (using 'delete' button in the stonith resource page) and sbd is disabled
        • user removes a group or a clone or a cloned group containing the last effective stonith resource in the cluster and sbd is disabled
        • disabling stonith resources is not supported in web ui, therefore this scenario doesn't apply
      • the error can be overridden
      • effective stonith resource is a stonith resource which
        • is not disabled
        • is capable of fencing (for example, fence_kdump is not capable of fencing)

       

              rhn-support-nhostako Nina Hostakova
              watson-automation Watson Automation
              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: