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]: Setting storage class in DSPO for mariadb/minio fails due to indentation issues #508

Closed
HumairAK opened this issue Dec 12, 2023 · 0 comments · Fixed by #509
Closed
Labels
kind/bug Something isn't working triage/accepted

Comments

@HumairAK
Copy link
Contributor

The error in dspo logs when storageclass is set:

2023-12-12T17:57:07Z	ERROR	Reconciler error	{"controller": "datasciencepipelinesapplication", "controllerGroup": "datasciencepipelinesapplications.opendatahub.io", "controllerKind": "DataSciencePipelinesApplication", "DataSciencePipelinesApplication": {"name":"sample","namespace":"dspa"}, "namespace": "dspa", "name": "sample", "reconcileID": "2eaa4e56-1f1d-4c46-8599-c1d081c9db52", "error": "error loading template (minio/pvc.yaml.tmpl) yaml: error converting YAML to JSON: yaml: line 11: did not find expected key"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:326
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234

this is because the storageClassName indent is wrong so the spec doesn't recognize this field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working triage/accepted
Development

Successfully merging a pull request may close this issue.

1 participant