Nextcloud upgrade warning management

[DavidePrincipi]

Nextcloud 31 upgrade shows database row format warning on migrated installations.

After upgrading to Nextcloud 31 (app version 1.5.0), installations originally deployed with NC24 or earlier (typically migrated from NS7) may display a warning in the admin interface about the database row format. While harmless, this warning may trigger unnecessary support requests.

Action items:

• Add a manual DB-fix procedure (script link) to the README and release notes of milestone 8.6
• Starting from NC32 evaluate including the DB-fix script in the module's bin/ directory for manual execution. The script can fix also other warning.
• Test upgrades to future Nextcloud 32 starting from NC23 with all intermediate major versions.

Context

https://help.nextcloud.com/t/frequent-nextcloud-31-hub-10-update-issues/214983#p-641010-new-database-check-incorrect-row-format-5

A database row format warning appears after upgrading Nextcloud to version 31 (Hub 10), especially when the original installation dates back to version 24 or earlier. This affects NS8 systems migrated from NS7. While the warning does not break functionality, it's visible in the admin UI and might cause confusion or support requests. A community-provided script can fix the issue by converting the database to use dynamic row format.

There's agreement that updates shouldn't apply potentially long-running DB fixes, but documenting a manual solution or optionally providing a script could help.

Discussion

• https://mattermost.nethesis.it/nethserver/pl/srt4w88r5iraxkqwk7tqbjqgsc
• https://community.nethserver.org/t/upgrade-to-nextcloud-hub-10-31-0-6-incorrect-row-format-found-in-your-database/25959

---

Thanks to Greavette, @mrmarkuz

[mrmarkuz]

target is 1.5.2-dev.1

Test case 1: Fresh install

• Install and configure Nextcloud testing
• Browse to Administration settings on the top right
• There should be a warning: "One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations."
• Execute the optimize script:
  runagent -m nextcloud1 nextcloud-db-optimize
• Refresh the Administration settings page
• The warning should be gone and there should be no errors in the logs

Test case 2: Migrated Nextcloud from NS7

• Install Nextcloud 24 on NS7
  yum install nethserver-nextcloud-1.20.2-1.ns7
• Upgrade to every major version (NC25, NC26, etc) until you reach the most recent for NS7 (1.22.5-1), see spec file for the versions.
  yum update nethserver-nextcloud-1.21.0-1.ns7
• Migrate Nextcloud to NS8
• Upgrade Nextcloud on NS8 via Software Center step by step until you reach the latest version 1.5.1, see NS8 Nextcloud releases.
• Upgrade to Nextcloud testing
• Browse to Administration settings on the top right
• There should be some warnings:

• Execute the optimize script:
  runagent -m nextcloud1 nextcloud-db-optimize
• Refresh the Administration settings page
• The warnings should be gone and there should be no errors in the logs

[stephdl]

case 1 verified
case 2 verified