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

[BUG] Runtime helm release stuck in "pending-install" status #2764

Closed
TrafalgarZZZ opened this issue Mar 20, 2023 · 0 comments · Fixed by #2765
Closed

[BUG] Runtime helm release stuck in "pending-install" status #2764

TrafalgarZZZ opened this issue Mar 20, 2023 · 0 comments · Fixed by #2765
Labels
bug Something isn't working

Comments

@TrafalgarZZZ
Copy link
Member

What is your environment(Kubernetes version, Fluid version, etc.)

Describe the bug
Runtime helm release stuck in "pending-install" status.

  1. Run helm install <release_name> /charts/<runtime>, it shows the helm release is in deployed status
  2. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant