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

files stuck in postprocessing state after upload #322

Closed
wkloucek opened this issue Jun 16, 2023 · 2 comments · Fixed by #364
Closed

files stuck in postprocessing state after upload #322

wkloucek opened this issue Jun 16, 2023 · 2 comments · Fixed by #364
Labels
Category:Defect Existing functionality is not working as expected Severity:sev2-high operations severely restricted, workaround available

Comments

@wkloucek
Copy link
Contributor

wkloucek commented Jun 16, 2023

Currently oCIS 3.0.0 has a bug that prevents it from working with nats-js as a store for the postprocessing setting (owncloud/ocis#6547).

Since this is our default:

https://github.com/owncloud/ocis-charts/blob/f034590fc1a72c9459df649e1e867ced90af0fe0/charts/ocis/values.yaml#L99C7-L105

oCIS with this Chart does not run out of the box.

There are multiple options to make it run:

  • use a different store than nats-js, for eg. Redis see add redis deployment example #323
  • use no store, by setting store.type to noop. As a consequence oCIS cannot be scaled anymore. Restarting the postprocessing pod might make files stuck in the postprocessing step. Your user notifications in the Web UI will not survive restarts of the userlog and eventshistory pod.
@wkloucek wkloucek added Severity:sev2-high operations severely restricted, workaround available Category:Defect Existing functionality is not working as expected labels Jun 16, 2023
@wkloucek
Copy link
Contributor Author

will be fixed with the upcoming oCIS 3.1.0-next.3 release (because it includes owncloud/ocis#6578)

@wkloucek wkloucek mentioned this issue Jul 3, 2023
11 tasks
@wkloucek wkloucek pinned this issue Jul 3, 2023
@wkloucek
Copy link
Contributor Author

The fix didn't make it into 3.1.0-next.3 but for sure will make it into 3.1.0

@wkloucek wkloucek mentioned this issue Jul 19, 2023
11 tasks
@wkloucek wkloucek unpinned this issue Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Defect Existing functionality is not working as expected Severity:sev2-high operations severely restricted, workaround available
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant