Description of problem: The packageserver pods deployed failed. [jzhang@dhcp-140-18 ocp-19]$ oc get pods NAME READY STATUS RESTARTS AGE catalog-operator-7fc5d98dbd-vf5rc 1/1 Running 0 5h9m olm-operator-75558c6d7-rt5hg 1/1 Running 0 5h9m olm-operators-ldt4l 1/1 Running 0 5h9m [jzhang@dhcp-140-18 ocp-19]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE packageserver.v0.8.1 Package Server 0.8.1 Installing [jzhang@dhcp-140-18 payload]$ oc describe csv ... Last Transition Time: 2019-02-19T06:25:45Z Last Update Time: 2019-02-19T07:36:18Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting The logs of the olm-operators: time="2019-02-19T06:25:39Z" level=info msg="could not query for GVK in api discovery" err=Unauthorized group=packages.apps.redhat.com kind=PackageManifest version=v1alpha1 Version-Release number of selected component (if applicable): OLM build commit id: cce4af21efb662527a8f71d22f7f2c37007ea4bf How reproducible: always Steps to Reproduce: 1. Install the OCP 4.0 via openshift-installer. Actual results: The packageservice pods deployed failed. And, no APIservice generated. [jzhang@dhcp-140-18 payload]$ oc get apiservice|grep package [jzhang@dhcp-140-18 payload]$ [jzhang@dhcp-140-18 payload]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE packageserver.v0.8.1 Package Server 0.8.1 Installing [jzhang@dhcp-140-18 payload]$ oc get pods NAME READY STATUS RESTARTS AGE catalog-operator-7fc5d98dbd-vf5rc 1/1 Running 0 5h24m olm-operator-75558c6d7-rt5hg 1/1 Running 0 5h24m olm-operators-ldt4l 1/1 Running 0 5h24m Expected results: The packageservice can be deployed successfully. Additional info: 1) Here are the olm-operator logs: ... time="2019-02-19T06:25:39Z" level=info msg="syncing CSV" csv=packageserver.v0.8.1 id=Lm094 namespace=openshift-operator-lifecycle-manager phase=Succeeded time="2019-02-19T06:25:39Z" level=info msg="checking packageserver.v0.8.1" time="2019-02-19T06:25:39Z" level=info msg="csv in operatorgroup" csv=packageserver.v0.8.1 id=IdIP3 namespace=openshift-operator-lifecycle-manager phase=Succeeded time="2019-02-19T06:25:39Z" level=info msg="could not query for GVK in api discovery" err=Unauthorized group=packages.apps.redhat.com kind=PackageManifest version=v1alpha1 time="2019-02-19T06:25:39Z" level=warning msg="unhealthy component: APIServices not installed" csv=packageserver.v0.8.1 id=IdIP3 namespace=openshift-operator-lifecycle-manager phase=Succeeded strategy=deployment time="2019-02-19T06:25:39Z" level=info msg="error updating ClusterServiceVersion status: Operation cannot be fulfilled on clusterserviceversions.operators.coreos.com \"packageserver.v0.8.1\": the object has been modified; please apply your changes to the latest version and try again" csv=packageserver.v0.8.1 id=Lm094 namespace=openshift-operator-lifecycle-manager phase=Succeeded time="2019-02-19T06:25:39Z" level=info msg="retrying openshift-operator-lifecycle-manager/packageserver.v0.8.1" E0219 06:25:39.586937 1 queueinformer_operator.go:155] Sync "openshift-operator-lifecycle-manager/packageserver.v0.8.1" failed: error updating ClusterServiceVersion status: Operation cannot be fulfilled on clusterserviceversions.operators.coreos.com "packageserver.v0.8.1": the object has been modified; please apply your changes to the latest version and try again ... 2)APIservice part in ConfigMap info: [jzhang@dhcp-140-18 payload]$ oc get cm olm-operators -o yaml |grep apiservicedefinitions -A 5 \ apiservicedefinitions:\n owned:\n - group: packages.apps.redhat.com\n \ version: v1alpha1\n kind: PackageManifest\n displayName: PackageManifest\n description: A PackageManifest is a resource generated from existing CatalogSources and their ConfigMaps\n deploymentName: packageserver\n \ containerPort: 5443" customResourceDefinitions: "" 3)Below is the full description info: [jzhang@dhcp-140-18 payload]$ oc describe csv packageserver.v0.8.1 Name: packageserver.v0.8.1 Namespace: openshift-operator-lifecycle-manager Labels: <none> Annotations: olm.operatorGroup=olm-operators olm.operatorNamespace=openshift-operator-lifecycle-manager olm.targetNamespaces=openshift-operator-lifecycle-manager API Version: operators.coreos.com/v1alpha1 Kind: ClusterServiceVersion Metadata: Creation Timestamp: 2019-02-19T02:23:20Z Generation: 1 Resource Version: 210768 Self Link: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-operator-lifecycle-manager/clusterserviceversions/packageserver.v0.8.1 UID: 5311e44d-33ed-11e9-a241-02673226e332 Spec: Apiservicedefinitions: Owned: Container Port: 5443 Deployment Name: packageserver Description: A PackageManifest is a resource generated from existing CatalogSources and their ConfigMaps Display Name: PackageManifest Group: packages.apps.redhat.com Kind: PackageManifest Name: Version: v1alpha1 Customresourcedefinitions: Description: Represents an Operator package that is available from a given CatalogSource which will resolve to a ClusterServiceVersion. Display Name: Package Server Install: Spec: Cluster Permissions: Rules: API Groups: Resources: configmaps Verbs: get list watch API Groups: operators.coreos.com Resources: catalogsources Verbs: get list watch API Groups: packages.apps.redhat.com Resources: packagemanifests Verbs: get list Service Account Name: packageserver Deployments: Name: packageserver Spec: Replicas: 2 Selector: Match Labels: App: packageserver Strategy: Type: RollingUpdate Template: Metadata: Labels: App: packageserver Spec: Containers: Command: /bin/package-server -v=4 --secure-port 5443 --global-namespace openshift-operator-lifecycle-manager Image: registry.svc.ci.openshift.org/ocp/4.0-2019-02-18-160525@sha256:8218f66ab676194f55cd625c3ff873617b5f94fba02aa46326b040d56790508f Image Pull Policy: Always Liveness Probe: Http Get: Path: /healthz Port: 5443 Scheme: HTTPS Name: packageserver Ports: Container Port: 5443 Readiness Probe: Http Get: Path: /healthz Port: 5443 Scheme: HTTPS Node Selector: Beta . Kubernetes . Io / Os: linux Node - Role . Kubernetes . Io / Master: Service Account Name: packageserver Tolerations: Operator: Exists Strategy: deployment Install Modes: Supported: true Type: OwnNamespace Supported: true Type: SingleNamespace Supported: true Type: MultiNamespace Supported: true Type: AllNamespaces Keywords: packagemanifests olm packages Links: Name: Package Server URL: https://github.com/operator-framework/operator-lifecycle-manager/tree/master/pkg/package-server Maintainers: Email: openshift-operators Name: Red Hat Maturity: alpha Min Kube Version: 1.11.0 Provider: Name: Red Hat Version: 0.8.1 Status: Certs Last Updated: 2019-02-19T06:25:47Z Certs Rotate At: 2021-02-17T06:25:45Z Conditions: Last Transition Time: 2019-02-19T02:23:20Z Last Update Time: 2019-02-19T02:23:20Z Message: requirements not yet checked Phase: Pending Reason: RequirementsUnknown Last Transition Time: 2019-02-19T02:23:20Z Last Update Time: 2019-02-19T02:23:20Z Message: one or more requirements couldn't be found Phase: Pending Reason: RequirementsNotMet Last Transition Time: 2019-02-19T02:23:21Z Last Update Time: 2019-02-19T02:23:21Z Message: all requirements found, attempting install Phase: InstallReady Reason: AllRequirementsMet Last Transition Time: 2019-02-19T02:23:23Z Last Update Time: 2019-02-19T02:23:23Z Message: waiting for install components to report healthy Phase: Installing Reason: InstallSucceeded Last Transition Time: 2019-02-19T02:23:23Z Last Update Time: 2019-02-19T02:23:26Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting Last Transition Time: 2019-02-19T02:24:25Z Last Update Time: 2019-02-19T02:24:25Z Message: install strategy completed with no errors Phase: Succeeded Reason: InstallSucceeded Last Transition Time: 2019-02-19T06:25:39Z Last Update Time: 2019-02-19T06:25:39Z Message: APIServices not installed Phase: Failed Reason: ComponentUnhealthy Last Transition Time: 2019-02-19T06:25:40Z Last Update Time: 2019-02-19T06:25:40Z Message: APIServices not installed Phase: Pending Reason: NeedsReinstall Last Transition Time: 2019-02-19T06:25:43Z Last Update Time: 2019-02-19T06:25:43Z Message: all requirements found, attempting install Phase: InstallReady Reason: AllRequirementsMet Last Transition Time: 2019-02-19T06:25:45Z Last Update Time: 2019-02-19T06:25:45Z Message: waiting for install components to report healthy Phase: Installing Reason: InstallSucceeded Last Transition Time: 2019-02-19T06:25:45Z Last Update Time: 2019-02-19T06:25:48Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting Last Transition Time: 2019-02-19T06:25:45Z Last Update Time: 2019-02-19T07:55:04Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting Requirement Status: Group: operators.coreos.com Kind: ClusterServiceVersion Message: CSV minKubeVersion (1.11.0) less than server version (v1.12.4+1221cce) Name: packageserver.v0.8.1 Status: Present Version: v1alpha1 Group: apiregistration.k8s.io Kind: APIService Message: Name: v1alpha1.packages.apps.redhat.com Status: DeploymentFound Version: v1 Dependents: Group: rbac.authorization.k8s.io Kind: PolicyRule Message: cluster rule:{"verbs":["get","list","watch"],"apiGroups":[""],"resources":["configmaps"]} Status: Satisfied Version: v1beta1 Group: rbac.authorization.k8s.io Kind: PolicyRule Message: cluster rule:{"verbs":["get","list","watch"],"apiGroups":["operators.coreos.com"],"resources":["catalogsources"]} Status: Satisfied Version: v1beta1 Group: rbac.authorization.k8s.io Kind: PolicyRule Message: cluster rule:{"verbs":["get","list"],"apiGroups":["packages.apps.redhat.com"],"resources":["packagemanifests"]} Status: Satisfied Version: v1beta1 Group: Kind: ServiceAccount Message: Name: packageserver Status: Present Version: v1 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal AllRequirementsMet 1h (x2 over 5h) operator-lifecycle-manager all requirements found, attempting install Normal InstallSucceeded 1h (x2 over 5h) operator-lifecycle-manager waiting for install components to report healthy
There two packageserver pods generated after I deleted its subscription, csv. [jzhang@dhcp-140-18 payload]$ oc get pods NAME READY STATUS RESTARTS AGE catalog-operator-7fc5d98dbd-vf5rc 1/1 Running 0 5h55m olm-operator-75558c6d7-s7mrt 1/1 Running 0 8m38s olm-operators-ldt4l 1/1 Running 0 5h54m packageserver-66bf7cc7fd-txj97 1/1 Running 0 5m5s packageserver-66bf7cc7fd-xfpxw 1/1 Running 0 5m5s [jzhang@dhcp-140-18 payload]$ oc get sub NAME PACKAGE SOURCE CHANNEL packageserver packageserver olm-operators alpha [jzhang@dhcp-140-18 payload]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE packageserver.v0.8.1 Package Server 0.8.1 Succeeded [jzhang@dhcp-140-18 payload]$ oc get ip NAME CSV SOURCE APPROVAL APPROVED install-sczpm packageserver.v0.8.1 Automatic true [jzhang@dhcp-140-18 payload]$ oc get apiservice|grep package v1alpha1.packages.apps.redhat.com openshift-operator-lifecycle-manager/v1alpha1-packages-apps-redhat-com True 6m28s [jzhang@dhcp-140-18 payload]$ oc get packagemanifest NAME AGE packageserver 5h Seems it works well after deleting the sub/csv excepted two pods generated. Added the "beta2blocker" label since I think it's a serious issue. Correct me if I'm wrong.
> Seems it works well after deleting the sub/csv excepted two pods generated. My mistake, the pod numbers as expected. Its replicas: 2 ... nodeSelector: beta.kubernetes.io/os: linux node-role.kubernetes.io/master: ""
So, from the CSV status, it seems that packageserver was running for about 4 hours before the APIService was deleted. OLM then attempted to recreate the APIService and it looks like it succeeded, after which it got stuck in an Installing state. This happens if the APIService is deleted immediately after OLM creates it. It would be really helpful to see deletion events and the ServiceAccount responsible. Is there any way we can get this info; kube-controller-manager logs maybe?
Nick, > Is there any way we can get this info; kube-controller-manager logs maybe? As below, hope it helps. mac:ocp-19 jianzhang$ oc logs openshift-kube-controller-manager-ip-10-0-175-83.us-east-2.compute.internal -n openshift-kube-controller-manager|grep package I0220 02:32:52.809682 1 garbagecollector.go:408] processing item [operators.coreos.com/v1alpha1/ClusterServiceVersion, namespace: , name: packageserver.v0.8.1, uid: 222ae1fa-341e-11e9-8be6-0667fd887256] E0220 02:32:53.807965 1 garbagecollector.go:313] error syncing item &garbagecollector.node{identity:garbagecollector.objectReference{OwnerReference:v1.OwnerReference{APIVersion:"operators.coreos.com/v1alpha1", Kind:"ClusterServiceVersion", Name:"packageserver.v0.8.1", UID:"222ae1fa-341e-11e9-8be6-0667fd887256", Controller:(*bool)(0xc420f75730), BlockOwnerDeletion:(*bool)(0xc420f75731)}, Namespace:""}, dependentsLock:sync.RWMutex{w:sync.Mutex{state:0, sema:0x0}, writerSem:0x0, readerSem:0x0, readerCount:1, readerWait:0}, dependents:map[*garbagecollector.node]struct {}{(*garbagecollector.node)(0xc4267a94a0):struct {}{}, (*garbagecollector.node)(0xc4267b74a0):struct {}{}, (*garbagecollector.node)(0xc4267c61e0):struct {}{}}, deletingDependents:false, deletingDependentsLock:sync.RWMutex{w:sync.Mutex{state:0, sema:0x0}, writerSem:0x0, readerSem:0x0, readerCount:0, readerWait:0}, beingDeleted:false, beingDeletedLock:sync.RWMutex{w:sync.Mutex{state:0, sema:0x0}, writerSem:0x0, readerSem:0x0, readerCount:0, readerWait:0}, virtual:false, virtualLock:sync.RWMutex{w:sync.Mutex{state:0, sema:0x0}, writerSem:0x0, readerSem:0x0, readerCount:0, readerWait:0}, owners:[]v1.OwnerReference(nil)}: Namespace parameter required. Based on my understanding, the SA/APIservice objects created by the OLM. So, after the delectation, does the OLM try to recreate them? I got nothing when checking the olm-operator/catalog-operator logs. Correct me if I'm wrong. > It would be really helpful to see deletion events and the ServiceAccount responsible. Yes, but the event will be preserved 1 hour as default, do you know how to check all the events from the system etcd? After running a couple of hours, the SA was lost too. Details: [jzhang@dhcp-140-18 openshift]$ oc get pods NAME READY STATUS RESTARTS AGE catalog-operator-7fc5d98dbd-vf5rc 1/1 Running 0 23h olm-operator-75558c6d7-s7mrt 1/1 Running 1 17h olm-operators-ldt4l 1/1 Running 0 23h [jzhang@dhcp-140-18 openshift]$ oc get sub NAME PACKAGE SOURCE CHANNEL packageserver packageserver olm-operators alpha [jzhang@dhcp-140-18 openshift]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE etcdoperator.v0.9.2 etcd 0.9.2 etcdoperator.v0.9.0 Succeeded packageserver.v0.8.1 Package Server 0.8.1 Pending [jzhang@dhcp-140-18 openshift]$ oc describe csv packageserver.v0.8.1 Name: packageserver.v0.8.1 Namespace: openshift-operator-lifecycle-manager Labels: <none> Annotations: olm.operatorGroup=olm-operators olm.operatorNamespace=openshift-operator-lifecycle-manager olm.targetNamespaces=openshift-operator-lifecycle-manager API Version: operators.coreos.com/v1alpha1 Kind: ClusterServiceVersion Metadata: Creation Timestamp: 2019-02-19T08:12:43Z Generation: 1 Resource Version: 977788 Self Link: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-operator-lifecycle-manager/clusterserviceversions/packageserver.v0.8.1 UID: 222ae1fa-341e-11e9-8be6-0667fd887256 Spec: Apiservicedefinitions: Owned: Container Port: 5443 Deployment Name: packageserver Description: A PackageManifest is a resource generated from existing CatalogSources and their ConfigMaps Display Name: PackageManifest Group: packages.apps.redhat.com Kind: PackageManifest Name: Version: v1alpha1 Customresourcedefinitions: Description: Represents an Operator package that is available from a given CatalogSource which will resolve to a ClusterServiceVersion. Display Name: Package Server Install: Spec: Cluster Permissions: Rules: API Groups: Resources: configmaps Verbs: get list watch API Groups: operators.coreos.com Resources: catalogsources Verbs: get list watch API Groups: packages.apps.redhat.com Resources: packagemanifests Verbs: get list Service Account Name: packageserver Deployments: Name: packageserver Spec: Replicas: 2 Selector: Match Labels: App: packageserver Strategy: Type: RollingUpdate Template: Metadata: Labels: App: packageserver Spec: Containers: Command: /bin/package-server -v=4 --secure-port 5443 --global-namespace openshift-operator-lifecycle-manager Image: registry.svc.ci.openshift.org/ocp/4.0-2019-02-18-160525@sha256:8218f66ab676194f55cd625c3ff873617b5f94fba02aa46326b040d56790508f Image Pull Policy: Always Liveness Probe: Http Get: Path: /healthz Port: 5443 Scheme: HTTPS Name: packageserver Ports: Container Port: 5443 Readiness Probe: Http Get: Path: /healthz Port: 5443 Scheme: HTTPS Node Selector: Beta . Kubernetes . Io / Os: linux Node - Role . Kubernetes . Io / Master: Service Account Name: packageserver Tolerations: Operator: Exists Strategy: deployment Install Modes: Supported: true Type: OwnNamespace Supported: true Type: SingleNamespace Supported: true Type: MultiNamespace Supported: true Type: AllNamespaces Keywords: packagemanifests olm packages Links: Name: Package Server URL: https://github.com/operator-framework/operator-lifecycle-manager/tree/master/pkg/package-server Maintainers: Email: openshift-operators Name: Red Hat Maturity: alpha Min Kube Version: 1.11.0 Provider: Name: Red Hat Version: 0.8.1 Status: Certs Last Updated: 2019-02-19T10:25:52Z Certs Rotate At: 2021-02-17T10:25:50Z Conditions: Last Transition Time: 2019-02-19T08:12:43Z Last Update Time: 2019-02-19T08:12:43Z Message: requirements not yet checked Phase: Pending Reason: RequirementsUnknown Last Transition Time: 2019-02-19T08:12:43Z Last Update Time: 2019-02-19T08:12:44Z Message: one or more requirements couldn't be found Phase: Pending Reason: RequirementsNotMet Last Transition Time: 2019-02-19T08:12:46Z Last Update Time: 2019-02-19T08:12:46Z Message: all requirements found, attempting install Phase: InstallReady Reason: AllRequirementsMet Last Transition Time: 2019-02-19T08:12:48Z Last Update Time: 2019-02-19T08:12:48Z Message: waiting for install components to report healthy Phase: Installing Reason: InstallSucceeded Last Transition Time: 2019-02-19T08:12:48Z Last Update Time: 2019-02-19T08:12:50Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting Last Transition Time: 2019-02-19T08:13:05Z Last Update Time: 2019-02-19T08:13:05Z Message: install strategy completed with no errors Phase: Succeeded Reason: InstallSucceeded Last Transition Time: 2019-02-19T08:25:39Z Last Update Time: 2019-02-19T08:25:39Z Message: installing: Waiting: waiting for deployment packageserver to become ready: Waiting for rollout to finish: 1 of 2 updated replicas are available... Phase: Failed Reason: ComponentUnhealthy Last Transition Time: 2019-02-19T08:25:39Z Last Update Time: 2019-02-19T08:25:39Z Message: installing: Waiting: waiting for deployment packageserver to become ready: Waiting for rollout to finish: 1 of 2 updated replicas are available... Phase: Pending Reason: NeedsReinstall Last Transition Time: 2019-02-19T08:25:41Z Last Update Time: 2019-02-19T08:25:41Z Message: all requirements found, attempting install Phase: InstallReady Reason: AllRequirementsMet Last Transition Time: 2019-02-19T08:25:42Z Last Update Time: 2019-02-19T08:25:42Z Message: waiting for install components to report healthy Phase: Installing Reason: InstallSucceeded Last Transition Time: 2019-02-19T08:25:42Z Last Update Time: 2019-02-19T08:25:46Z Message: installing: Waiting: waiting for deployment packageserver to become ready: Waiting for rollout to finish: 1 out of 2 new replicas have been updated... Phase: Installing Reason: InstallWaiting Last Transition Time: 2019-02-19T08:26:17Z Last Update Time: 2019-02-19T08:26:17Z Message: install strategy completed with no errors Phase: Succeeded Reason: InstallSucceeded Last Transition Time: 2019-02-19T10:18:57Z Last Update Time: 2019-02-19T10:18:57Z Message: APIServices not installed Phase: Failed Reason: ComponentUnhealthy Last Transition Time: 2019-02-19T10:18:58Z Last Update Time: 2019-02-19T10:18:58Z Message: install strategy completed with no errors Phase: Succeeded Reason: InstallSucceeded Last Transition Time: 2019-02-19T10:25:44Z Last Update Time: 2019-02-19T10:25:44Z Message: APIServices not installed Phase: Failed Reason: ComponentUnhealthy Last Transition Time: 2019-02-19T10:25:47Z Last Update Time: 2019-02-19T10:25:47Z Message: APIServices not installed Phase: Pending Reason: NeedsReinstall Last Transition Time: 2019-02-19T10:25:48Z Last Update Time: 2019-02-19T10:25:48Z Message: all requirements found, attempting install Phase: InstallReady Reason: AllRequirementsMet Last Transition Time: 2019-02-19T10:25:50Z Last Update Time: 2019-02-19T10:25:50Z Message: waiting for install components to report healthy Phase: Installing Reason: InstallSucceeded Last Transition Time: 2019-02-19T10:25:50Z Last Update Time: 2019-02-19T10:25:54Z Message: APIServices not installed Phase: Installing Reason: InstallWaiting Last Transition Time: 2019-02-19T10:26:21Z Last Update Time: 2019-02-19T10:26:21Z Message: install strategy completed with no errors Phase: Succeeded Reason: InstallSucceeded Last Transition Time: 2019-02-19T10:32:42Z Last Update Time: 2019-02-19T10:32:42Z Message: requirements no longer met Phase: Failed Reason: RequirementsNotMet Last Transition Time: 2019-02-19T10:32:42Z Last Update Time: 2019-02-19T10:32:42Z Message: APIServices not installed Phase: Pending Reason: NeedsReinstall Last Transition Time: 2019-02-19T10:32:42Z Last Update Time: 2019-02-19T10:32:42Z Message: one or more requirements couldn't be found Phase: Pending Reason: RequirementsNotMet Last Transition Time: 2019-02-19T10:32:42Z Last Update Time: 2019-02-20T01:58:18Z Message: one or more requirements couldn't be found Phase: Pending Reason: RequirementsNotMet Requirement Status: Group: operators.coreos.com Kind: ClusterServiceVersion Message: CSV minKubeVersion (1.11.0) less than server version (v1.12.4+1221cce) Name: packageserver.v0.8.1 Status: Present Version: v1alpha1 Group: apiregistration.k8s.io Kind: APIService Message: Name: v1alpha1.packages.apps.redhat.com Status: DeploymentFound Version: v1 Group: Kind: ServiceAccount Message: Service account does not exist Name: packageserver Status: NotPresent Version: v1 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal RequirementsNotMet 1h (x27819 over 17h) operator-lifecycle-manager one or more requirements couldn't be found Normal RequirementsNotMet 4m (x2301 over 1h) operator-lifecycle-manager one or more requirements couldn't be found
*** Bug 1678924 has been marked as a duplicate of this bug. ***
This is not a bug in OLM, but with GC. I've closed as a duplicate and pointed to the tracking issue for the GC bug. *** This bug has been marked as a duplicate of bug 1679309 ***
Hit this issue again in the cluster. [core@ip-10-0-134-56 ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-25-234632 True False 153m Cluster version is 4.0.0-0.nightly-2019-02-25-234632 [core@ip-10-0-134-56 ~]$ oc get pods NAME READY STATUS RESTARTS AGE catalog-operator-9d4cb8db9-2tz2f 1/1 Running 0 168m olm-operator-6d85b99b8-wg4t2 1/1 Running 0 168m olm-operators-b4zgx 1/1 Running 0 168m [core@ip-10-0-134-56 ~]$ oc get sub NAME PACKAGE SOURCE CHANNEL packageserver packageserver olm-operators alpha [core@ip-10-0-134-56 ~]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE packageserver.v0.8.1 Package Server 0.8.1 Pending OLM image info: io.openshift.build.commit.id=1ac9ace63034ea90f31e5ad33435d3f5476c7d85 io.openshift.build.commit.url=https://github.com/operator-framework/operator-lifecycle-manager/commit/1ac9ace63034ea90f31e5ad33435d3f5476c7d85 io.openshift.build.source-location=https://github.com/operator-framework/operator-lifecycle-manager About the GC issue, bug 1679309 comment 18 for details.
https://github.com/operator-framework/operator-lifecycle-manager/pull/729 This PR may fix part of the problem