db1175 has a discrepancy between puppet and reality:
MariaDB root@(none):(none)> select @@binlog_format; +-----------------+ | @@binlog_format | +-----------------+ | MIXED | +-----------------+
db1175 has a discrepancy between puppet and reality:
MariaDB root@(none):(none)> select @@binlog_format; +-----------------+ | @@binlog_format | +-----------------+ | MIXED | +-----------------+
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | jcrespo | T376916 Upgrade backup hosts to Debian Bookworm 12.X | |||
| Resolved | jcrespo | T383902 Upgrade backup source or mediabackup database host os to Debian bookworm or decommission them | |||
| Unknown Object (Task) | |||||
| Resolved | Marostegui | T373579 Productionize db22[21-40] | |||
| Resolved | ABran-WMF | T378503 mariadb::binlog_format: 'ROW' not effective on m5/db1175 |
I am not sure if I am missing context here:
cumin2024@db1175.eqiad.wmnet[(none)]> show global variables like 'binlog_format'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | binlog_format | ROW | +---------------+-------+ 1 row in set (0.035 sec) cat hieradata/hosts/db1175.yaml # db1175 mariadb::shard: 's3' mariadb::binlog_format: 'ROW'
either I have missed something or it has been changed in the interval. this issue is now fixed then!