Skip to content

FailedCreate replicaset/catalog-operator and replicaset/olm-operator #1586

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

Closed
kirankumar-mahi opened this issue Jun 22, 2020 · 6 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@kirankumar-mahi
Copy link

kirankumar-mahi commented Jun 22, 2020

Hi There,

I am not able to install OLM 0.15.1 on the Kubernetes cluster 1.18.4

Steps executed - >

Step1 -

$ curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.15.1/install.sh | bash -s 0.15.1

failed with errors.

Waiting for deployment "olm-operator" rollout to finish: 0 of 1 updated replicas are available...
Waiting for deployment "olm-operator" rollout to finish: 0 of 1 updated replicas are available...
error: deployment "olm-operator" exceeded its progress deadline

olm 2s Warning FailedCreate replicaset/catalog-operator-67f885b8f5 Error creating: Timeout: request did not complete within requested timeout 34s
olm 77s Warning FailedCreate replicaset/catalog-operator-67f885b8f5 Error creating: Timeout: request did not complete within requested timeout
olm 9m13s Normal ScalingReplicaSet deployment/catalog-operator Scaled up replica set catalog-operator-67f885b8f5 to 1
olm 2s Warning FailedCreate replicaset/olm-operator-665576bb4 Error creating: Timeout: request did not complete within requested timeout 34s
olm 9m13s Normal ScalingReplicaSet deployment/olm-operator Scaled up replica set olm-operator-665576bb4 to 1

Environment ->

  1. operator-lifecycle-manager release 0.15.1

  2. go version go1.14.4 linux/amd64

  3. Kubectl version :

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.4", GitCommit:"c96aede7b5205121079932896c4ad89bb93260af", GitTreeState:"clean", BuildDate:"2020-06-17T11:41:22Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.4", GitCommit:"c96aede7b5205121079932896c4ad89bb93260af", GitTreeState:"clean", BuildDate:"2020-06-17T11:33:59Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

  1. uname -a ->

Linux 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

@exdx exdx added kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jun 23, 2020
@exdx
Copy link
Member

exdx commented Jun 23, 2020

Kind of hard to tell what's going on based on these logs -- is it possible the pod was not able to be scheduled?

I know it's kind of tricky, but is there any more information that you can provide us with? Was this a local cluster or in the cloud? We run our e2e tests on kind clusters to capture upstream kube-related issues, so issues like this one are important to us. OLM should be able to install and run just fine on vanilla kube.

@kirankumar-mahi
Copy link
Author

kirankumar-mahi commented Jun 25, 2020

Its local kubernetes cluster. Its failure creating replicaset. This happened in kubernetes 1.18.4 version. But when I tried on kubernetes 1.18.0 version, it worked.

@stale
Copy link

stale bot commented Aug 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 24, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Aug 25, 2020
@stale
Copy link

stale bot commented Oct 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Dec 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@timflannagan
Copy link
Member

It looks like we don't have enough information to debug this failed installation further, so I'm going to close this out in the meantime. Let's re-open this if we can reproduce this failure using newer OLM minor version releases, and attach any necessary debugging information then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

4 participants