Nextcloud upgrade from 1.6.1 may leave the instance in maintenance mode

[stephdl]

Steps to reproduce

• Install ns8-nextcloud version 1.6.1.
• Upgrade to the 1.7.1 that includes the changesnectloud NC33.
• During the upgrade, check the service startup order:
  • nextcloud-redis.service + nextcloud-db.service
  • nextcloud-app.service
  • nextcloud-notify_push.service
  • nextcloud-nginx.service
• Verify that MariaDB is really ready before nextcloud-app.service starts.
• Verify that the update waits for Nextcloud initialization and occ upgrade to complete.

Expected behavior

The upgrade should complete successfully without leaving Nextcloud in maintenance mode or with a pending database upgrade.

Services should start in the correct order: Redis/MariaDB first, then Nextcloud app, then dependent services.

Actual behavior

During a major upgrade, the update process can continue too early while Nextcloud is still initializing or running occ upgrade.

This can cause wrong service ordering, premature restarts, and leave Nextcloud in a broken state such as maintenance=true or needsDbUpgrade=true.

Components

• NS8
• ns8-nextcloud 1.6.1 → 1.7.1

See also

• PR #228
• https://community.nethserver.org/t/nextcloud-update-failed/27880
• Bug: post-restore script 20configure fails on line 39 - Nextcloud database not ready #7988

[stephdl]

QA

• Install Nextcloud 1.6.1.
• Upgrade to image ghcr.io/nethserver/nextcloud:1.7.2-dev.1.
• Verify the upgrade completes successfully.
• Verify Nextcloud is not left with:
  occ status
  • maintenance=true
  • needsDbUpgrade=true
• Verify service startup order:
  • nextcloud-redis.service and nextcloud-db.service first
  • nextcloud-app.service next
  • nextcloud-notify_push.service and nextcloud-nginx.service last
• Verify MariaDB is accepting connections before nextcloud-app.service starts.
• Verify Nextcloud web UI is reachable after upgrade.
• Verify login works.
• Verify file browsing/upload works.