search

openyurtio / yurt-app-manager

The workload controller manager from NodePool level in OpenYurt cluster
Apache License 2.0
6 stars 1 forks source link

[BUG] helm install fails with INSTALLATION FAILED: failed pre-install: timed out waiting for the condition #138

Closed fujitatomoya closed 1 year ago

fujitatomoya commented 1 year ago

What happened:

helm install yurt-app-manager -n kube-system yurt-app-manager/charts/yurt-app-manager/ fails with timeout.

What you expected to happen:

Successfully complete deployment for yurt-app-manager.

How to reproduce it (as minimally and precisely as possible):

# helm install yurt-app-manager -n kube-system yurt-app-manager/charts/yurt-app-manager/ --debug
install.go:194: [debug] Original chart version: ""
install.go:211: [debug] CHART PATH: /root/yurt-app-manager/charts/yurt-app-manager

client.go:133: [debug] creating 1 resource(s)
install.go:154: [debug] CRD nodepools.apps.openyurt.io is already present. Skipping.
client.go:133: [debug] creating 1 resource(s)
install.go:154: [debug] CRD uniteddeployments.apps.openyurt.io is already present. Skipping.
client.go:133: [debug] creating 1 resource(s)
install.go:154: [debug] CRD yurtappdaemons.apps.openyurt.io is already present. Skipping.
client.go:133: [debug] creating 1 resource(s)
install.go:154: [debug] CRD yurtappsets.apps.openyurt.io is already present. Skipping.
client.go:133: [debug] creating 1 resource(s)
install.go:154: [debug] CRD yurtingresses.apps.openyurt.io is already present. Skipping.
client.go:477: [debug] Starting delete for "yurt-app-manager-admission" ServiceAccount
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "yurt-app-manager-admission" ClusterRole
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "yurt-app-manager-admission" ClusterRoleBinding
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "yurt-app-manager-admission" Role
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "yurt-app-manager-admission" RoleBinding
client.go:133: [debug] creating 1 resource(s)
client.go:477: [debug] Starting delete for "yurt-app-manager-admission-create" Job
client.go:133: [debug] creating 1 resource(s)
client.go:703: [debug] Watching for changes to Job yurt-app-manager-admission-create with timeout of 5m0s
client.go:731: [debug] Add/Modify event for yurt-app-manager-admission-create: ADDED
client.go:770: [debug] yurt-app-manager-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:731: [debug] Add/Modify event for yurt-app-manager-admission-create: MODIFIED
client.go:770: [debug] yurt-app-manager-admission-create: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
helm.go:84: [debug] failed pre-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
    helm.sh/helm/v3/cmd/helm/install.go:141
github.com/spf13/cobra.(*Command).execute
    github.com/spf13/cobra@v1.6.1/command.go:916
github.com/spf13/cobra.(*Command).ExecuteC
    github.com/spf13/cobra@v1.6.1/command.go:1044
github.com/spf13/cobra.(*Command).Execute
    github.com/spf13/cobra@v1.6.1/command.go:968
main.main
    helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
    runtime/proc.go:250
runtime.goexit
    runtime/asm_amd64.s:1571

Anything else we need to know?:

Environment:

others

/kind bug

huiwq1990 commented 1 year ago

@fujitatomoya As the log shows, I can not find why timeout. Maybe the pull images cost too much, or some pods run failed.

You can check by these methods:

1) increase helm install timeout setting by add the flag --timeout, https://helm.sh/docs/intro/using_helm/#helpful-options-for-installupgraderollback

2) find if any job failed

kubectl get job -n kube-system

3) find if any pod failed

kubectl get pod -n kube-system
fujitatomoya commented 1 year ago

@huiwq1990 thanks for the information, i will try that out and get back to you.

fujitatomoya commented 1 year ago

@huiwq1990 adding timeout does help, thanks for the information, i will go ahead to close this issue.