-
Notifications
You must be signed in to change notification settings - Fork 7k
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
unable to build kubernetes objects from release manifest: BuildConfig / ImageStream #7073
Comments
Does this only happen on a dry run or does it also happen on a normal install? Resources that are not core resources need to be pulled down and cached. I am curious helm has talked with the kuberentes API prior to performing this operation. |
@mattfarina hi. This happens in both cases:
|
|
@danielefranceschi hello! Thank you for your help. It works in this way:
The ticket can be closed! I would add this documentation. But, I do not know where. @danielefranceschi thank you! |
Glad to help :) I'm not a go+k8s-api expert (yet), but I'd like to make an hypotesis: IMHO the cause is that the implementation of Lines 55 to 56 in 9b42702
Line 229 in 9b42702
OpenShift client 1 RH, I hate you and your backward-compatibility policy with legacy stuff |
Closing as issue answered. |
Hey @Andrei-Stepanov , I tested with your configuration and I am still getting the same exception. client.go:87: [debug] creating 8 resource(s)
install.go:312: [debug] Install failed and atomic is set, uninstalling release
uninstall.go:91: [debug] uninstall: Deleting cl
client.go:220: [debug] Starting delete for "claim-frontend" Service
client.go:220: [debug] Starting delete for "claim-backend" Service
client.go:220: [debug] Starting delete for "claim-frontend" Deployment
client.go:220: [debug] Starting delete for "claim-backend" Deployment
client.go:220: [debug] Starting delete for "claim-ng-frontend" ConfigMap
client.go:220: [debug] Starting delete for "claim-ng-backend" ConfigMap
client.go:220: [debug] Starting delete for "php_fpm_buildConfig_1" BuildConfig
client.go:245: [debug] buildconfigs.build.openshift.io "php_fpm_buildConfig_1" not found
client.go:220: [debug] Starting delete for "php-fpm-1" ImageStream
uninstall.go:124: [debug] purge requested for cl
Error: release cl failed, and has been uninstalled due to atomic being set: BuildConfig in version "v1" cannot be handled as a BuildConfig: v1.BuildConfig.Spec: v1.BuildConfigSpec.CommonSpec: NodeSelector: ReadString: expects " or n, but found t, error found in #10 byte of ...|anbuild":true},"outp|..., bigger context ...|BuildsHistoryLimit":3,"nodeSelector":{"canbuild":true},"output":{"to":{"kind":"ImageStreamTag","name|...
helm.go:76: [debug] BuildConfig in version "v1" cannot be handled as a BuildConfig: v1.BuildConfig.Spec: v1.BuildConfigSpec.CommonSpec: NodeSelector: ReadString: expects " or n, but found t, error found in #10 byte of ...|anbuild":true},"outp|..., bigger context ...|BuildsHistoryLimit":3,"nodeSelector":{"canbuild":true},"output":{"to":{"kind":"ImageStreamTag","name|...
release cl failed, and has been uninstalled due to atomic being set
helm.sh/helm/v3/pkg/action.(*Install).failRelease
/home/circleci/helm.sh/helm/pkg/action/install.go:320
helm.sh/helm/v3/pkg/action.(*Install).Run
/home/circleci/helm.sh/helm/pkg/action/install.go:279
main.runInstall
/home/circleci/helm.sh/helm/cmd/helm/install.go:209
main.newInstallCmd.func1
/home/circleci/helm.sh/helm/cmd/helm/install.go:115
github.com/spf13/cobra.(*Command).execute
/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
/home/circleci/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
/usr/local/go/src/runtime/proc.go:203
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357
apiVersion: build.openshift.io/v1
kind: BuildConfig
apiVersion: image.openshift.io/v1
kind: ImageStream Can you please advice on this ?, otherways reopen this issue. Thanks. |
@younes0925 hello. You have different error message than I had. Sounds like you have something wrong in template. You can post your template. Or look at my :
|
Hello, please help to deploy templates with OpenShift resources:
The text was updated successfully, but these errors were encountered: