Upgrade from 27.1.4.1 to 27.1.6.2 FAILED - Stuck in maintenance mode about nextcloud-snap HOT 8 CLOSED

Welcome and thanks for your request.

If turning off maintenance mode see FAQ doesn't do the trick, I'd suggest you revert as described here and wait for the devs to do their magic.

from nextcloud-snap.

@Pilzinsel64 has had a similar issue see #2641 and already posted upstream.

from nextcloud-snap.

Hi @scubamuc, thanks for your input and the info you posted. Definitely useful, revert helped me. I don't think it's related to #2641 which is around a problem when some files (web root) cannot be located (during or after an upgrade).

In contrast, here the problem seems to be that a file that is known and can be located (/snap/nextcloud/XXX/htdocs/.htaccess) is read-only and the upgrade process was never designed to handle this situation gracefully so it just exits prematurely and leaves the instance in maintenance mode.

After rollback, these are the relevant mounts in the system under test:

$ mount | grep -E '(/snap/nextcloud/39216|/snap/nextcloud/40247)'

/var/lib/snapd/snaps/nextcloud_39216.snap on /snap/nextcloud/39216 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
/var/lib/snapd/snaps/nextcloud_40247.snap on /snap/nextcloud/40247 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide)
/dev/sda1 on /snap/nextcloud/40247/conf/ssl.conf type ext4 (rw,relatime,x-systemd.before=snap.nextcloud.apache.service)
/dev/sda1 on /snap/nextcloud/40247/htdocs/.htaccess type ext4 (rw,relatime,x-systemd.before=snap.nextcloud.apache.service)
/dev/sda1 on /snap/nextcloud/39216/htdocs/.htaccess type ext4 (rw,relatime,x-systemd.before=snap.nextcloud.apache.service)
/dev/sda1 on /snap/nextcloud/39216/conf/ssl.conf type ext4 (rw,relatime,x-systemd.before=snap.nextcloud.apache.service)

The error message is spurious (I definitely did not have a full disk) and I theorise that the mount holding the given .htaccess file, normally mounted rw (as above), is removed during the upgrade, and the error is generated because this removed mount shadows the same file from another mount which is a read-only squashfs.

from nextcloud-snap.

That bug was introduced in 27.1.5, we caught it (#2631) and reported it, and it was fixed in 27.1.6 (nextcloud/server#42385). I'm running this just fine, why is it deciding to break for you?

from nextcloud-snap.

I'm amd64, and it appears that you're arm64, which is really the only obvious difference. @nextcloud-snap/triagers any chance one of you running on arm64 can duplicate this?

from nextcloud-snap.

@pachulo is running on arm64...

from nextcloud-snap.

Yes, my production instance runs on arm64, but I didn't experience this when upgrading from 26.0.10 to 27.1.6, so I don't really know what's going on here...

from nextcloud-snap.

OK, thanks everyone, I'll keep en eye on things and re-open if needed.

from nextcloud-snap.