mariadb 10.6 config not compatible with latest Nextcloud #7

Closed
opened 2021-05-12 14:08:42 +00:00 by decentral1se · 7 comments
Owner

The latest tag has a new version of mariadb which makes this error fail installation on a new deployment:

InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE

Looks like we need to configure something.

The latest tag has a new version of mariadb which makes this error fail installation on a new deployment: > InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE Looks like we need to configure something.
Author
Owner

Rolling back to 10.5 works for now 🤦

Rolling back to 10.5 works for now 🤦
Author
Owner

FYI @3wordchant the bot is now automatically doing merges for upgrades and releases without question (haven't had time to refine it yet) so this happened 89eb579618. There are ways of tweaking this process which we can discuss soon.

FYI @3wordchant the bot is now automatically doing merges for upgrades and releases without question (haven't had time to refine it yet) so this happened https://git.autonomic.zone/coop-cloud/nextcloud/commit/89eb579618202d7cfcc4e32865f1b557ae2ef1a7. There are ways of tweaking this process which we can discuss soon.
Owner

Yeah I've been meaning to ask about the workflow. It seems if I run abra recipe .. release locally then the bot will make dupe commits? Anyway, is there a way to stop auto-updating MariaDB temporarily on this repo til we have chance to see what's up with this issue? 🤔

Yeah I've been meaning to ask about the workflow. It seems if I run `abra recipe .. release` locally then the bot will make dupe commits? Anyway, is there a way to stop auto-updating MariaDB temporarily on this repo til we have chance to see what's up with this issue? 🤔
Author
Owner

The bot won't make a dupe commit, it just runs recipe ... release as you would, so the logic is just the same? If it sees that there is a new tag, then it makes that release, but if it sees that we're on latest, nothing is done.

It seems like we can use ignoreDeps something like {"ignoreDeps": ["mariadb"]} but then I dont know if we want to configure it from Renovate side? Perhaps we could add an additional file which recipe ... release would read and if it finds a match, it will ignore this release?

I guess we need to map out the existing automation and see what is working and what isn't. Handiest way to stop this now is comment it out from https://git.autonomic.zone/autonomic-cooperative/renovate-bot/src/branch/main/config.js.tmpl and then redeploy renovate with https://git.autonomic.zone/autonomic-cooperative/renovate-bot#deploy.

The bot won't make a dupe commit, it just runs `recipe ... release` as you would, so the logic is just the same? If it sees that there is a new tag, then it makes that release, but if it sees that we're on latest, nothing is done. It seems like we can use [ignoreDeps](https://docs.renovatebot.com/configuration-options/#ignoredeps) something like `{"ignoreDeps": ["mariadb"]}` but then I dont know if we want to configure it from Renovate side? Perhaps we could add an additional file which `recipe ... release` would read and if it finds a match, it will ignore this release? I guess we need to map out the existing automation and see what is working and what isn't. Handiest way to stop this now is comment it out from https://git.autonomic.zone/autonomic-cooperative/renovate-bot/src/branch/main/config.js.tmpl and then redeploy renovate with https://git.autonomic.zone/autonomic-cooperative/renovate-bot#deploy.
Author
Owner

Maybe 8dfad23470 fixes it for now? Opened up https://git.autonomic.zone/coop-cloud/abra/issues/205 also.

Maybe https://git.autonomic.zone/coop-cloud/nextcloud/commit/8dfad23470694e04b5e97f36257992cfec1fc434 fixes it for now? Opened up https://git.autonomic.zone/coop-cloud/abra/issues/205 also.
Author
Owner

Hmmm we did see https://git.autonomic.zone/coop-cloud/nextcloud/pulls/10#issuecomment-7333 but I think that doesn't confirm that 8dfad23470 really works but for now, this is solved. https://git.autonomic.zone/coop-cloud/abra/issues/205 will address the larger issue in the release logic, will close for now.

Hmmm we did see https://git.autonomic.zone/coop-cloud/nextcloud/pulls/10#issuecomment-7333 but I think that doesn't confirm that https://git.autonomic.zone/coop-cloud/nextcloud/commit/8dfad23470694e04b5e97f36257992cfec1fc434 really works but for now, this is solved. https://git.autonomic.zone/coop-cloud/abra/issues/205 will address the larger issue in the release logic, will close for now.
Author
Owner

It looks like it might be possible to upgrade and set some backwards compatible flag but I don't think I care enough to do that right now. Leaving this for potential upgrade futures.

- https://github.com/nextcloud/docker/issues/1536 - https://github.com/nextcloud/server/issues/25436#issuecomment-883213001 It looks like it might be possible to upgrade and set some backwards compatible flag but I don't think I care enough to do that right now. Leaving this for potential upgrade futures.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#7
No description provided.