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

This was a synchronization bug between the MariaDB engine and the system manager (systemd), this leads to service status does not match the MariaDB's real state.

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

    • None
    • Important
    • rhel-databases
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      After a WSREP State Transfer on the cluster nodes, the MariaDB service did not switch the service state to the correct state.

      What is the impact of this issue to you?

      This leads administrators to believe the node was still syncing, causing them to hesitate in routing traffic to it or fearing the synchronization has frozen.

      Please provide the package NVR for which the bug is seen:

      mariadb-server-10.11.10-1.el9_6.x86_64

      How reproducible is this bug?:

      Always.

      Steps to reproduce

      1. Freshly install RHEL9
      2. Install mariadb-server-galera-10.11.15-1.module+el9.7.0+23768+0a6844e9(or mariadb-server-galera-10.11.10-1.module+el9.5.0+22578+dc54e53f)and configure MariaDB galera cluster.
      3. Take one node offline and then rejoin it.

      Expected results

      After the WSREP state transfer is complete, the status should be marked as finished, not remain ongoing.

      Actual results

      The status remains ongoing even after the WSREP state transfer is complete.

              mschorm@redhat.com Michal Schorm
              rhn-support-qguo Qi Guo
              Michal Schorm Michal Schorm
              Vaclav Danek Vaclav Danek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: