Galera node leaves the cluster after an INSERT that adds INTERVAL partitions on another node

--source include/galera_cluster.inc

--source include/have_partition.inc

--source include/have_innodb.inc

--connection node_1

SET timestamp= UNIX_TIMESTAMP('2026-05-02 00:00:00');

--error 0,ER_PARSE_ERROR,ER_PARTITIONS_MUST_BE_DEFINED_ERROR

CREATE TABLE t1 (a INT, c DATE, PRIMARY KEY (a, c)) ENGINE=InnoDB PARTITION BY RANGE COLUMNS (c) INTERVAL 1 DAY (PARTITION p0 VALUES LESS THAN ('2026-04-30'));

if ($mysql_errno)

{

  --skip Needs RANGE COLUMNS ... INTERVAL partitioning

}

# The INSERT adds the partitions up to the current date on node 1

INSERT INTO t1 VALUES (1, '2026-05-01');

--connection node_2

# Wait for the row on node 2. Error 1242 means that it is not there yet

--let $i= 100

while ($i)

{

  --error 0,ER_SUBQUERY_NO_1_ROW,ER_UNKNOWN_COM_ERROR,ER_LOCK_WAIT_TIMEOUT,ER_LOCK_DEADLOCK,2006,2013

  SELECT IF(COUNT(*) = 1, 1, (SELECT 1 UNION SELECT 2)) INTO @found FROM t1;

  --let $err= $mysql_errno

  if ($err != 1242)

  {

    --let $i= 1

  }

  if ($err == 1242)

  {

    --sleep 0.1

  }

  --dec $i

}

if ($err == 1242)

{

  --die Node 2 does not have the row that node 1 inserted

}

if ($err)

{

  --die Node 2 left the cluster: it could not apply a row that went into a partition added by INTERVAL partitioning on node 1

}

--connection node_1

DROP TABLE t1;

mysqltest: At line 40: Node 2 left the cluster: it could not apply a row that went into a partition added by INTERVAL partitioning on node 1

2026-10-07 10:00:45 2 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table test.t1; Table has no partition for value from column_list, Error_code: 1526; handler error HA_ERR_NO_PARTITION_FOUND; the event's master log FIRST, end_log_pos 0, Internal MariaDB error code: 1526

2026-10-07 10:00:45 2 [ERROR] WSREP: Inconsistency detected: Inconsistent by consensus on bee85299-c1d9-11f1-b197-b7970b3590a4:4

2026-10-07 10:00:45 0 [Note] WSREP: Received SELF-LEAVE. Closing connection.

2026-10-07 10:00:45 2 [ERROR] WSREP: Failed to apply write set: gtid: bee85299-c1d9-11f1-b197-b7970b3590a4:4 server_id: bee8184f-c1d9-11f1-b103-b7055afc0fd9 client_id: 12 trx_id: 60 flags: 3 (start_transaction | commit)