Open jvillafanez opened 8 years ago
There are quite some issues in core: https://github.com/owncloud/core/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+constraint+violation
I however can not reproduce this, so not sure what this is about. Seems like your DB does not read commited entries accross transactions
Tests are run against a default installation of mysql. Other than resetting the mysql password, I don't see any other change.
Can you check the transaction isolation level? https://github.com/owncloud/core/issues/20555#issuecomment-157331571
mysql> SELECT @@GLOBAL.tx_isolation, @@tx_isolation;
+-----------------------+-----------------+
| @@GLOBAL.tx_isolation | @@tx_isolation |
+-----------------------+-----------------+
| REPEATABLE-READ | REPEATABLE-READ |
+-----------------------+-----------------+
1 row in set (0.00 sec)
Something to fix in the docker image...
I've changed the mysql startup command to add the --transaction-isolation=READ-COMMITTED
. I've checked it's set in the DB correctly; currently running tests
It's still happening.
Still happening with current master? We now have a check on the admin page regarding the transaction isolation level when it is not correct. So in case you still get the error, please check the admin page if the warning is displayed.
Is READ-COMMITTED
the expected isolation level?
We'll need to wait until the tests for 9.1 (the current master) are ready. We'll keep an eye on this.
CC: @SergioBertolinSG
This is happening from time to time in several versions of ownCloud.
Checked with 8.1.3, 8.2.0 and 9.0 (this last one after upgrading from 8.0.6)
@nickvergessen I don't know how we want to handle this but I haven't seen a full successful run in all the environments yet.