Skip to content

Helm panics with an unknown storage driver #13127

@mattfarina

Description

@mattfarina

Output of helm version: 3.15.2

Output of kubectl version: N/A

Cloud Provider/Platform (AKS, GKE, Minikube etc.): N/A

When there is an unknown storage driver (for helm releases) there is a panic. For example...

$ HELM_DRIVER=foo helm help
panic: Unknown driver in HELM_DRIVER: foo

goroutine 1 [running]:
helm.sh/helm/v3/pkg/action.(*Configuration).Init(0xc00057a140, {0x2559598, 0xc0001dcfc0}, {0x2085221, 0x7}, {0xc00001201c, 0x3}, 0x2354a58)
	helm.sh/helm/v3/pkg/action/action.go:419 +0x7b9
main.main.func1()
	helm.sh/helm/v3/cmd/helm/helm.go:75 +0x7b
github.com/spf13/cobra.(*Command).preRun(...)
	github.com/spf13/cobra@v1.8.0/command.go:1017
github.com/spf13/cobra.(*Command).execute(0xc000696308, {0x368d8e0, 0x0, 0x0})
	github.com/spf13/cobra@v1.8.0/command.go:927 +0x5a2
github.com/spf13/cobra.(*Command).ExecuteC(0xc000418008)
	github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.8.0/command.go:1039
main.main()
	helm.sh/helm/v3/cmd/helm/helm.go:83 +0x209

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions