[Bug]: Database error on Update

[Erebus999]

⚠️ 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

Das Datenbankschema wird aktualisiert

Exception: Database error when running migration 28000Date20230906104802 for app core Index name "configkey" for table "oc_preferences" collides with the constraint on table "oc_appconfig".

Steps to reproduce

1. Update Database on Upate to V28

Expected behavior

Exception: Database error when running migration 28000Date20230906104802 for app core Index name "configkey" for table "oc_preferences" collides with the constraint on table "oc_appconfig".

Installation method

Community Manual installation with Archive

Nextcloud Server version

28

Operating system

Other

PHP engine version

PHP 8.2

Web server

Apache (supported)

Database engine version

MySQL

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

Updated from a MINOR version (ex. 22.1 to 22.2)

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[SystemKeeper]

Is this really MySQL or Postgres?

[Erebus999]

'dbtype' => 'mysql',
Is specified by the Provider

[joshtrichards]

That migration also doesn't touch that table.

And the only migration that should even be touching the named tables is a completely different one:

server/core/Migrations/Version13000Date20170718121200.php

Line 313 in c734a18

if (!$schema->hasTable('preferences')) {

See #42173 for something similar with the same migration but also hitting an unrelated table.

Or do I need more coffee? ☕

[joshtrichards]

Duplicate of #41253