[primary storage on Openstack swift] Update to 12.0.5 / 13RC breaks Nextcloud #8041
Comments
ChristophWurst
added
bug
0. Needs triage
|
Any news? This is kind of a big deal. |
|
I reverted back to 12.0.4 as this bug is a deal breaker for nextcloud usage. |
|
I find it amazing to not have an answer from anyone (even just to ask for more information). It's a serious issue, and it's kind of ignored. A minor update just completely broke the nextcloud installation, but hey, no big deal, this affects only few people, no worry. |
|
I am actually holding off performing the upgrade because of this issue that "affects only few people" -- I currently don't have the luxury of spending time on rolling back if something goes wrong (I am in charge of 4 Nextcloud systems). Would like to see some insights in this ticket to inspire confidence to perform the update. That confidence is currently missing. |
Hi Arvi, I totally understand your frustration about your broken NC server due to the minor update to 12.0.5. @ChristophWurst @MorrisJobke @jospoortvliet @rullzer Who can help? Quite a few users broke their installation by updating to 12.0.5 Please advise. |
|
Updating the server instance is always a total mess! Minor or major update is always trouble ! |
|
I can't find the bug I think this is... Anyway. Could you try:
@skjnldsv @juliushaertl I think #8078 would help here as well. |
|
mm I don't have any appdata folder, where is it supposed to be? |
|
@Arvi89 in your |
|
Yeah, I don't have that folder. |
|
Ah right then your data folder is indeed empty I guess. I can try to come up with a SQL query... because if you just purge it from the DB on object store it will just create new items :) |
DELETE
FROM oc_filecache
WHERE path LIKE 'appdata%/js/%'
OR path LIKE 'appdata%/css/%';Try that. Of course make sure you have a backup and all that ;) |
|
No luck. The query was executed properly (203 rows affected), but it doesn't work better. |
|
That is strange... and nothing in your log files? |
|
|
|
Any news about this (serious) issue ? |
|
So, long story short I have no idea. As I tried several upgrades and they all didn't work. If somebody could get me an account on a system with this bug maybe I could debug better. |
|
So what is the actual recommendation? |
|
@rullzer Did you try a server with primary storage on swift? That seems the mutual item for people suffering from the bug? |
|
I confirm using swift as primary storage. |
|
I don't have a test system with swift..... I'll see if I can come up with something. But it won't be this week I'm afraid. |
|
Well, the sooner the better, I still can't use my nextcloud storage, and I don't want to revert to 12.0.4 as I'm worried to lose data. |
|
I'm experiencing the same problem with the 12.0.5 update. Also, I tried on a test environment to upgrade a 12.0.4 Nextcloud instance using OpenStack Swift as primary storage to the latest RC of NextCloud 13, and it has the same problem. |
harryhb
changed the title
|
I guess we should be looking towards the Openstack swift implementation as the root cause? I changed the title of this issue to reflect. Additionally added 13RC as impacted version |
|
I just wrote a small app to help here: Could you try:
|
|
Did all that, it didnt fix the issue. |
harryhb
changed the title
|
I'm experiencing the same issue. Nextcloud doesn't show any graphics in the web-ui but seems to work in the background. I'm still receiving sync messages for example. See the screens below. All links to the graphics/theme disappeared somehow.
|
|
Yep, that's the issue. But it doesn't seem to worry the team more than that, which is weird as it makes the instance unusable. |
|
I have a similar experience. It looks like SWIFT backend is the culprit. I switch to use S3 backend and it went on well. I think NextCloud need to look at swift storage backend and work on it. Even mounting swift storage as external storage is unstable. Very frequently, it failed to upload a file. |
|
I can confirm that this issue is linked to swift as primary storage. |
|
Does somebody have a working swift setup for me to test against? Because the docker images I could find did not work. |
|
My setup was working with 12.0.4. Is it what you are asking ? |
|
And I can also confirm that this test instance is working fine with S3. |
|
For information, I have reverted the change done in this commit : |
What do you mean, you guys seriously still haven't installed a nextcloud instance with swift, really??? |
|
They are releasing a product with a feature that they can't test whether it works or not. It's amazing! |
|
@Schmuuu @skjnldsv why the thumbs down? it's the truth, otherwise this would have been a showstopper for a release, or at least I hope so. So nothing what @tdttester said is wrong. |
|
Lets keep it civil people. We are constantly updating and extending our test cases. This test matrix is already big and getting bigger every day. We are in the process of setting up automated tests against swift right now. But this takes time and resources which are limited. Hopefully we have a fix for you to test soon. But comments like that don't make us work any faster. The opposite is more likely. |
|
Please note that I did not attack anybody personally. I also did not use any swear words, nor harsh language. Don't deflect by calling the truth uncivil. I know that it is hard to have test cases for every single edge case, but this doesn't change the fact that my comment above was correct. |
|
@tessus it's called diplomacy. Saying things sarcastically has never improved the dialogue between people.
Which one do you prefer? I made my choice :) |
|
@skjnldsv ok, my bad. I'm blunt and I expect others to be blunt with me as well. for me, all 3 sentences have the same meaning: I screwed up and thus have to fix it. But I agree with you, the second one may "sound" nicer to a lot of people. Personally I don't put value in how something sounds, but the context. Disclaimer: I have a genuine distaste for sugar-coating and making things sound nice for reasons of diplomacy and political correctness. I'm working on it, but it may take a while... ;-) Anyway, I don't want to derail this ticket any further. I just wanted to make my position clear. P.S.: I also love sarcasm. |
|
@tessus no worries. But yes, it's not about sugar coating things, it's about telling the other person you're with him to fix the issue (which is productive) and not focusing on the issue itself (which is counter-productive) :) |
|
I think this is the same issue as #8233 The fix should be trivial to apply on 13 and 12. Please test. I'll make sure it is backported if it fixes it. |
|
Yep, this is working. Adding the return statement fixed my problem! Thank you! |
|
I just manually updated to Nextcloud 13. Procedure like described in https://docs.nextcloud.com/server/13/admin_manual/maintenance/manual_upgrade.html |
Issue logged after discussion on support: https://help.nextcloud.com/t/broken-after-update-to-12-0-5/26300
Steps to reproduce
Expected behaviour
Upgrade script runs; through web interface the upgrade can be finalized and system is back up and running.
Actual behaviour
Server configuration
Operating system: Debian stable
Web server: Apache/2.4.25 (Debian)
Database: mariadb Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
PHP version: PHP 7.0.27-0+deb9u1
Nextcloud version: 12.0.5 / 13RC
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 12.0.4
Where did you install Nextcloud from: Through admin interface
Signing status: Not possible to login
List of activated apps:
App list
Enabled: - activity: 2.5.2 - admin_audit: 1.2.0 - bruteforcesettings: 1.0.3 - calendar: 1.5.7 - caniupdate: 0.1.1 - comments: 1.2.0 - contacts: 2.0.1 - dav: 1.3.1 - federatedfilesharing: 1.2.0 - federation: 1.2.0 - files: 1.7.2 - files_downloadactivity: 1.1.1 - files_pdfviewer: 1.1.1 - files_sharing: 1.4.0 - files_texteditor: 2.4.1 - files_trashbin: 1.2.0 - files_versions: 1.5.0 - files_videoplayer: 1.1.0 - firstrunwizard: 2.1 - gallery: 17.0.0 - logreader: 2.0.0 - lookup_server_connector: 1.0.0 - mail: 0.7.8 - metadata: 0.6.0 - nextcloud_announcements: 1.1 - notifications: 2.0.0 - oauth2: 1.0.5 - ocsms: 1.12.2 - passman: 2.1.4 - password_policy: 1.2.2 - provisioning_api: 1.2.0 - qownnotesapi: 17.5.0 - serverinfo: 1.2.0 - sharebymail: 1.2.0 - spreed: 2.0.2 - survey_client: 1.0.0 - systemtags: 1.2.0 - tasks: 0.9.5 - twofactor_backupcodes: 1.1.1 - updatenotification: 1.2.0 - workflowengine: 1.2.0Nextcloud configuration:
Config report
Are you using external storage, if yes which one: Primary storage on Openstack/Swift
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Firefox & Chromium
Operating system: Debian testing
Logs
Web server error log
Web server error log
No errorsNextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
ReferenceError: OC is not definedThe text was updated successfully, but these errors were encountered: