NC pod gets killed too fast during installation
A fresh install of NC (see #1020 (closed)) lead to this:
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Link issues together to show that they're related.
Learn more.
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Contributor
This currently uses the default probes from the Nextcloud chart. We can either raise the issue upstream or override the probes in our helm chart. I'd love to trust upstream in this case, but maybe it's not the wise option
So my proposal would be to add this to our values (as we have it overwritten in stackspin/stackspin right now):
nextcloud: startupProbe: enabled: true failureThreshold: 60
- Maarten de Waard changed milestone to %0.8.2
changed milestone to %0.8.2
- Contributor
Can be done in conjunction with #965 (closed)
- Maarten de Waard assigned to @maarten
assigned to @maarten
- Maarten de Waard mentioned in issue #965 (closed)
mentioned in issue #965 (closed)
- Maarten de Waard unassigned @maarten
unassigned @maarten
- Maarten de Waard mentioned in merge request !157 (merged)
mentioned in merge request !157 (merged)
- Arie Peterson mentioned in commit 979a17fe
mentioned in commit 979a17fe
- Arie Peterson closed with merge request !157 (merged)
closed with merge request !157 (merged)
Please register or sign in to reply