mariadb 10.6 config not compatible with latest Nextcloud #7
Closed
opened 2021-05-12 14:08:42 +00:00 by decentral1se
·
7 comments
No Branch/Tag Specified
main
update_33.0.8
renovate/pgautoupgrade-pgautoupgrade-18.x
renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x
pr-15.2.0+34.0.2-fpm
pr-14.1.0+33.0.7-fpm
pr-14.2.0+33-fpm
pr-15.1.0+34.0.2-fpm
pr-15.0.0+34.0.2-fpm
pr-14.0.1+33.0.7-fpm
feat/check-major-upgrade
pr-14.0.0+33-fpm
temp
fix/nginx-conf-config-name
pr-13.2.0+32-fpm
renovate/redis-8.x
upload-limit
feature/imaginary
kc_stable
nextcloud-v28
add-theming-v28.0.5
add-theming
update-nginx-conf
split-bbb-onlyoffice-compos
split-onlyoffice-bbb-config
authentik_sso
healthchecks
occ_cmds
auto_app_install
embed_nextcloud_in_iframe
auto_configure_sso
add-postgres-db
14.1.1+33.0.8-fpm
14.1.0+33.0.7-fpm
14.0.1+33.0.7-fpm
14.0.0+33.0.7-fpm
13.2.0+32-fpm
13.1.5+32.0.13-fpm
13.1.4+32.0.13-fpm
13.1.3+32.0.13-fpm
13.1.2+32.0.13-fpm
13.1.1+32.0.12-fpm
13.1.0+32.0.11-fpm
13.0.1+32.0.3-fpm
13.0.0+32.0.3-fpm
12.1.0+31.0.6-fpm
12.0.1+31.0.6-fpm
12.0.0+31.0.6-fpm
11.4.0+30.0.6-fpm
11.4.0+30.0.10-fpm
11.3.0+30.0.6-fpm
11.2.0+30.0.6-fpm
11.1.0+30.0.6-fpm
11.0.1+30.0.4-fpm
11.0.0+30.0.4-fpm
10.0.0+30.0.4-fpm
9.2.0+29.0.8-fpm
6.0.11+28.0.10-fpm
6.0.10+28.0.10-fpm
6.0.9+28.0.10-fpm
9.1.2+29.0.5-fpm
6.0.8+28.0.5-fpm
6.0.7+28.0.5-fpm
9.1.0+29.0.5-fpm
9.0.0+29.0.5-fpm
6.0.6+28.0.5-fpm
8.0.1+29.0.3-fpm
8.0.0+29.0.1-fpm
7.0.3+29.0.1-fpm
6.0.5+28.0.5-fpm
7.0.2+29.0.1-fpm
7.0.1+29.0.1-fpm
7.0.0+29.0.0-fpm
6.0.4+28.0.5-fpm
6.0.3+28.0.5-fpm
6.0.2+28.0.5-fpm
5.0.3+27.0.1-fpm
6.0.1+28.0.2-fpm
6.0.0+28.0.1-fpm
5.2.0+27.1.5-fpm
5.1.1+27.1.5-fpm
5.1.0+27.1.3-fpm
5.0.2+27.0.1-fpm
5.0.1+27.0.1-fpm
5.0.0+27.0.0-fpm
4.0.7+26.0.2-fpm
4.0.6+26.0.2-fpm
4.0.5+26.0.2-fpm
4.0.4+26.0.2-fpm
4.0.3+26.0.2-fpm
4.0.2+26.0.2-fpm
4.0.1+26.0.1-fpm
4.0.0+26.0.1-fpm
3.3.2+25.0.6-fpm
3.3.1+25.0.5-fpm
3.3.0+25.0.5-fpm
3.2.0+25.0.4-fpm
3.1.2+25.0.4-fpm
3.1.1+25.0.1-fpm
3.1.0+25.0.1-fpm
3.0.1+25.0.1-fpm
3.0.0+25.0.1-fpm
2.1.4+24.0.6-fpm
2.1.3+24.0.5-fpm
2.1.2+24.0.3-fpm
2.1.1+24.0.2-fpm
2.1.0+24.0.0-fpm
2.0.0+23.0.4-fpm
1.0.0+23.0.1-fpm
No labels
Milestone
No items
No Milestone
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
BornDeleuze
Brooke
cas (Cassowary)
coopcloud
dannygroenewegen (Danny Groenewegen)
decentral1se (d1)
fauno (fauno)
ineiti (Linus Gasser)
javielico (Javielico)
jjsfunhouse
kawaiipunk (KawaiiPunk)
knoflook
moosemower
notplants
oxaliq (sorrel)
p4u1
renovate-bot (Comrade Renovate Bot)
stevensting
trav (Trav Fryer)
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/nextcloud#7
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The latest tag has a new version of mariadb which makes this error fail installation on a new deployment:
Looks like we need to configure something.
Rolling back to 10.5 works for now 🤦
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.
Yeah I've been meaning to ask about the workflow. It seems if I run
abra recipe .. releaselocally 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? 🤔The bot won't make a dupe commit, it just runs
recipe ... releaseas 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 whichrecipe ... releasewould 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.
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.
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.
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.