Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Error migrating from Nextcloud 27 to 28 #44106

Closed
5 of 8 tasks
csh4rp opened this issue Mar 9, 2024 · 1 comment
Closed
5 of 8 tasks

[Bug]: Error migrating from Nextcloud 27 to 28 #44106

csh4rp opened this issue Mar 9, 2024 · 1 comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug

Comments

@csh4rp
Copy link

csh4rp commented Mar 9, 2024

⚠️ This issue respects the following points: ⚠️

Bug description

When I run the migration for nextcloud from 27 to 28 this error occurs:

Updating database schema

Exception: Database error when running migration 28000Date20231004103301 for app core An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 4025 CONSTRAINT oc_file_metadata.metadata failed for nextcloud.oc_file_metadata

This migrations script seems to be only creating a table, so I'm not sure what's it all about.

Steps to reproduce

  1. Changed docker base image to 28-fpm
  2. Restarted nextcloud

Expected behavior

Application should be updated

Installation method

None

Nextcloud Server version

28

Operating system

RHEL/CentOS

PHP engine version

None

Web server

Nginx

Database engine version

MariaDB

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

None

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

@csh4rp csh4rp added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Mar 9, 2024
@csh4rp
Copy link
Author

csh4rp commented Mar 9, 2024

Turns out table file_metadata had stored location as text instead of json from one of mine devices and simply deleting this data that was not in JSON format fixed the issue. Still seems like a bug that either migration did not change it or that it was possible to put it there in the first place.

@csh4rp csh4rp closed this as completed Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback bug
Projects
None yet
Development

No branches or pull requests

2 participants