-
Notifications
You must be signed in to change notification settings - Fork 1.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 bundle-upgrade using operator-sdk cli tool #6204
Comments
Can you check by running the same command with an increased timeout using the |
hello, |
@talsharon48 just to make sure - you can't share any logs at all? Without some logs or more information I'm not quite sure we will be able to help very much. That said, I'll share a brief overview of what I would check:
I hope this helps a bit! |
@everettraven I can investigate the logs from any pod, ill just have to type here any figures manually for you to see.
Any other suggestions? or logs you need? |
@talsharon48 The only other thing I can think to check is if the If it does not then that means OLM is automatically approving the upgrade - I'm not sure what impact this has on the actual generation of a new If that doesn't seem to be causing the problem I can't really think of anything other reason why this issue is happening. Is it possible for you to provide a way that this problem can be replicated? If I can replicate the problem I can try to dig a bit further. |
@everettraven I would be thankful if you help me investigate the problem, I'll explain the steps I have done for you to replicate my problem:
Also changed the
To:
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Bug Report
What did you do?
Hello,
I am using operator-sdk v1.24.0 and trying to use it to create bundle and use them in openshift cluster via OLM.
i wrote a demo operator made bundle from it and created a catalog image using catalog-build and catalog-push.
i have manged to create catalog source from it, saw it in the UI and installed the operator, when i tried upgrading the operator, i have create new bundle version using make bundle VERSION=0.0.2, bundle-build and bundle-push and used operator-sdk upgrade bundle to upgrade it.
i have encountered an error saying "Failed to run bundle upgrage: install plan is not available for subscription : timed out waiting for condition" although when i browsing the catalog i can see the latest version is v0.0.2 and not v0.0.1.
when i uninstalled and installed manually the operator the desired v0.0.2 was deployed.
NOTE: i am working in on-premise environment that i cant upload any logs or code snippets.
What did you expect to see?
running operator-sdk upgrade-bundle command to deploy new version (CSV) of my operator.
What did you see instead? Under which circumstances?
after running the command a pod named was raised and served the new version
although nothing other happened and the error mentioned above was raised.
Environment
Operator type:
/language go
Kubernetes cluster type:
openshift v4.6.15
$ operator-sdk version
operator-sdk version: "v1.24.0", commit: "de6a14d03de3c36dcc9de3891af788b49d15f0f3", kubernetes version: "1.24.2", go version: "go1.18.6", GOOS: "linux", GOARCH: "amd64"
$ go version
(if language is Go)go version go1.18.6 linux/amd64
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"8df677dc147fe8297d90c4757154469a931bdb90", GitTreeState:"clean", BuildDate:"2022-11-04T15:44:27Z", GoVersion:"go1.17.10", Compiler:"gc", Platform:"linux/amd64"}
The text was updated successfully, but these errors were encountered: