You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your environment(Kubernetes version, Fluid version, etc.)
Describe the bug
Runtime helm release stuck in "pending-install" status.
Run helm install <release_name> /charts/<runtime>, it shows the helm release is in deployed status
Then run helm status <release_name>, the status of the release is still pending-install
Using --wait and --debug got the following error.
helm install --debug --wait -f /tmp/jfsdemo-juicefs-values.yaml3484361427 -n default jfsdemo charts/juicefs/
install.go:178: [debug] Original chart version: ""
install.go:195: [debug] CHART PATH: /charts/juicefs
client.go:128: [debug] creating 7 resource(s)
wait.go:48: [debug] beginning wait for 7 resources with timeout of 5m0s
install.go:416: [debug] failed to record the release: update: failed to update: secrets "sh.helm.release.v1.jfsdemo.v1" is forbidden: User "system:serviceaccount:fluid-system:juicefsruntime-controller" cannot update resource "secr
ets" in API group "" in the namespace "default"
NAME: jfsdemo
LAST DEPLOYED: Mon Mar 20 15:51:44 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
It seems it's a bug introduced in #2697 where the PR remove the permission to allow controller to update secret.
What you expect to happen:
How to reproduce it
Additional Information
The text was updated successfully, but these errors were encountered:
What is your environment(Kubernetes version, Fluid version, etc.)
Describe the bug
Runtime helm release stuck in "pending-install" status.
helm install <release_name> /charts/<runtime>
, it shows the helm release is indeployed
statushelm status <release_name>
, the status of the release is stillpending-install
Using
--wait
and--debug
got the following error.It seems it's a bug introduced in #2697 where the PR remove the permission to allow controller to update secret.
What you expect to happen:
How to reproduce it
Additional Information
The text was updated successfully, but these errors were encountered: