Public bug reported: The 8.0.18 version of mysql-8.0 has this upstream bug:
https://bugs.mysql.com/bug.php?id=97279 Note 8.0.17 did not display this bug. After a complete outage dba.rebootClusterFromCompleteOutage() errors with: output: "ERROR: Conflicting transaction sets between 10.5.0.55:3306 and 10.5.0.52:3306 Dba.rebootClusterFromCompleteOutage: Conflicting transaction sets between 10.5.0.55:3306 and 10.5.0.52:3306 (MYSQLSH 51152) at /tmp/tmpn2y5qo9l.js:3:12 in dba.rebootClusterFromCompleteOutage(); Steps to reproduce: Build a cluster Shut each node of the cluster down (reboot) Start mysql on each node Run dba.rebootClusterFromCompleteOutage() The cs:~openstack-charmers-next/mysql-innodb-cluster has a test zaza.openstack.charm_tests.mysql.tests.MySQLInnoDBClusterColdStartTest that re-creates the failure. Note: It is currently disabled due to this bug. ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854880 Title: Conflicting Transaction Sets following Complete Outage of InnoDB Cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1854880/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
