Demonium commented on issue #6670:
URL: https://github.com/apache/cloudstack/issues/6670#issuecomment-3023391512
Hello @DaanHoogland ,
I'm not an expert just discovering the whole stuff but follow this tutorial
https://severalnines.com/blog/mysql-innodb-cluster-80-complete-deployment-walk
DaanHoogland commented on issue #6670:
URL: https://github.com/apache/cloudstack/issues/6670#issuecomment-3023200819
thanks @Demonium , this is clearly an edge case. I am not sure about all the
right conditions yet. One thing is the cluster bit, that seems to play a role.
You are saying you
Demonium commented on issue #6670:
URL: https://github.com/apache/cloudstack/issues/6670#issuecomment-3020925303
Hello,
I have setup again cloudstack on a fresh database installation without setup
innodb cluster and it's work perfectly at first time I don't know if it's
relevant for you
DaanHoogland commented on issue #6670:
URL: https://github.com/apache/cloudstack/issues/6670#issuecomment-3018120870
so there are two issues here that both would not lead to problems in
isolation:
1. the default table type (ENGINE) should be set to innodb. this can be
documented as a pre
itsmdev opened a new issue, #6670:
URL: https://github.com/apache/cloudstack/issues/6670
Error log:
```
2022-08-24 02:14:35,802 ERROR [c.c.u.d.Merovingian2] (main:null) (logid:)
cleanupForServer:Exception:The table does not comply with the requirements by
an external plugin.
Demonium commented on issue #6670:
URL: https://github.com/apache/cloudstack/issues/6670#issuecomment-3017089724
Hello,
I just had the same issue on version 4.20 after a fresh installation...
I have executed the lines below to correct the issue
`ALTER TABLE cloud.op_lock ENGINE=INNOD
