Crashloopbackoff after update to 8.5.1
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- helm, kubernetes
- 领域
- devops, infrastructure
调研方向
首先比较 8.5.0 和 8.5.1 版本之间的 Helm chart 更改，然后检查 Nextcloud 升级期间的 pod 日志和 kubectl describe 输出。确认 liveness 和 readiness 探针是否在升级完成之前运行；当升级到 8.5.1 能够成功启动且没有 CrashLoopBackOff 时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Describe your Issue
After updating the chart from 8.5.0 to 8.5.1 the nextcloud pod won't successfully start.
It's entering a Crashloopbackoff-state.
Logs and Errors
The pods log itself states "Upgrading nextcloud from 32.0.0.13 ...."
kubectl describe pod nextcloud-6845ccd787-mrlbz returns this:
Normal Scheduled 8m44s default-scheduler Successfully assigned default/nextcloud-6845ccd787-mrlbz to bastet
Normal Pulled 8m44s kubelet Container image "quay.io/k8tz/k8tz:0.18.0" already present on machine
Normal Created 8m44s kubelet Created container: k8tz
Normal Started 8m44s kubelet Started container k8tz
Normal Pulling 8m43s kubelet Pulling image "nextcloud:32.0.1-apache"
Normal Pulled 7m20s kubelet Successfully pulled image "nextcloud:32.0.1-apache" in 1m22.692s (1m22.692s including waiting). Image size: 523993624 bytes.
Warning Unhealthy 4m34s (x9 over 7m4s) kubelet Liveness probe failed: Get "http://10.42.1.195:80/status.php": dial tcp 10.42.1.195:80: connect: connection refused
Normal Started 3m4s (x5 over 7m20s) kubelet Started container nextcloud
Normal Killing 2m34s (x5 over 6m44s) kubelet Container nextcloud failed liveness probe, will be restarted
Normal Created 2m4s (x6 over 7m20s) kubelet Created container: nextcloud
Warning Unhealthy 2m4s (x32 over 7m8s) kubelet Readiness probe failed: Get "http://10.42.1.195:80/status.php": dial tcp 10.42.1.195:80: connect: connection refused
Normal Pulled 2m4s (x5 over 6m13s) kubelet Container image "nextcloud:32.0.1-apache" already present on machine
I guess the upgrading isn't fast enough, so the liveness probe fails and therefore the pod gets restarted, which results in a loop. (hence Crashloopbackoff)
Describe your Environment
-
Kubernetes distribution: k3s
-
Helm Version (or App that manages helm): version.BuildInfo{Version:"v3.19.0", GitCommit:"3d8990f0836691f0229297773f3524598f46bda6", GitTreeState:"clean", GoVersion:"go1.24.6"}
-
Helm Chart Version: 8.5.1
-
values.yaml:
# paste your values.yaml (anonymize any sensitive data)
Additional context, if any
Not posting my values.yaml or other infos, since I think they're unnecessary.
Reverting back to 8.5.0 makes the nextcloud pod start up again.
Thx for your help & work.
If you need more info, please ask and I'll try provide it.
- 主要语言
- Go Template
- 星标
- 539
- 派生
- 316
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/helm 的其他 Issue
-
No native support for REDIS_USER enviroment var可能已有人在做 @jholmes802 于 15 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
Nextcloud pods run as the namespace's default service account: the chart's account is only created with rbac.enabled, which binds the removed PodSecurityPolicy可能已有人在做 @martin-mat 于 6 天前认领。 未关闭
难度 3/5 半天 新手友好度 55/100
-
nextcloud.openmetrics.allowedClients is silently ignored unless nextcloud.configs is set可能已有人在做 @JanWelker 于 31 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 78/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
MISP/misp-docker#478 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
IBM/cloud-pak-deployer#1205 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
nuts-foundation/nuts-admin#344 ·
维护者通常 5 天内回复
-
kind/engineering pulumi/pulumi-terraform Task Workflow Failure
难度 2/5 1-3 小时 新手友好度 64/100
pulumi/pulumi-terraform#1261 ·
维护者通常 1 天内回复
-
bug P5 XS
难度 2/5 1-3 小时 新手友好度 78/100
open-astro/AlpacaBridge#1550 ·
维护者通常 1 天内回复