[Bug]: Update from 30.0.4 to 30.0.6 fails with integrity check with no solution.

[piiskop]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

I gave the command to update from 30.0.4 to 30.0.6. It failed due to integrity problems. There was no link or button back or information what problems there exactly were.

Steps to reproduce

1. Have Nextcloud 30.0.4!
2. Have something that causes the integrity check to fail! I had something with mindmap.
3. Command to upgrade to 30.0.6!
4. See that the upgrade does not finish and there is no other way back than the back-button of the browser.

Expected behavior

There is displayed exact information how to solve the problem or what is even better - Nextcloud provides ways to solve it on its own.

Nextcloud Server version

30

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response