Bug 1852607 - ocs-operator csv hangs in Pending phase due to noobaa-metrics requirement not met
Summary: ocs-operator csv hangs in Pending phase due to noobaa-metrics requirement not...
Keywords:
Status: CLOSED DUPLICATE of bug 1851328
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jose A. Rivera
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-30 20:40 UTC by Coady LaCroix
Modified: 2020-06-30 21:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-30 21:01:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Coady LaCroix 2020-06-30 20:40:22 UTC
Description of problem (please be detailed as possible and provide log
snippests):

During a default ocs-ci deployment of OCS (AWS IPI) the ocs-operator csv creation hangs in pending state due to a missing dependency causing the ocs deployment to timeout (while using ocs-ci). 

NAME                            DISPLAY                       VERSION        REPLACES              PHASE
ocs-operator.v4.5.0-467.ci      OpenShift Container Storage   4.5.0-467.ci                         Pending

From oc get csv -o yaml :

status:
 conditions:
 - lastTransitionTime: "2020-06-30T18:58:22Z"
   lastUpdateTime: "2020-06-30T18:58:22Z"
   message: requirements not yet checked
   phase: Pending
   reason: RequirementsUnknown
 - lastTransitionTime: "2020-06-30T18:58:22Z"
   lastUpdateTime: "2020-06-30T18:58:22Z"
   message: one or more requirements couldn't be found
   phase: Pending
   reason: RequirementsNotMet

...

- dependents:
  - group: rbac.authorization.k8s.io
    kind: PolicyRule
    message: namespaced rule:{"verbs":["get","list","watch"],"apiGroups":[""],"resources":["services","endpoints","pods"]}
    status: NotSatisfied
    version: v1
  group: ""
  kind: ServiceAccount
  message: Policy rule not satisfied for service account
  name: noobaa-metrics
  status: PresentNotSatisfied




Version of all relevant components (if applicable):
ocs-operator: 4.5.0-467.ci


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
I am unable to deploy this version of OCS and unable to use/test it.


Is there any workaround available to the best of your knowledge?
No


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1 (default ocs-ci deployment)


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Did not try


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Run default ocs-ci deployment (AWS IPI using stable-4.5 ocs-operator version)
2. Wait for ocs-operator csv creation to timeout


Actual results:
ocs-operator csv hangs in pending phase and creation never succeeds

Expected results:
ocs-operator csv creation succeeds


Additional info:

The cluster in the following jenkins job is still running as of creating this bz if further troubleshooting is necessary.

Jenkins run: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/9323/
Logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/clacroix/clacroix_20200630T180706/
Kubeconfig: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/clacroix/clacroix_20200630T180706/openshift-cluster-dir/auth/kubeconfig
Must Gather: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/clacroix/clacroix_20200630T180706/logs/failed_testcase_ocs_logs_1593540799/deployment_ocs_logs/

Comment 2 Coady LaCroix 2020-06-30 21:01:03 UTC

*** This bug has been marked as a duplicate of bug 1851328 ***


Note You need to log in before you can comment on or make changes to this bug.