Bug 1807528

Summary:	OCS 4.2.1 operator dosen't install
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Valentino Uberti <vuberti>
Component:	ocs-operator	Assignee:	Nobody <nobody>
Status:	VERIFIED ---	QA Contact:	Elad <ebenahar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2	CC:	mattia.vernizzi, sostapov, tim.sterk
Target Milestone:	---	Keywords:	AutomationBackLog
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Valentino Uberti 2020-02-26 14:53:42 UTC

Description of problem (please be detailed as possible and provide log
snippests):

The ocs-operator dosen't install using the operator-hub

Version of all relevant components (if applicable):

OCP 4.3.1

ocs-operator.v4.2.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


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

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

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


Steps to Reproduce:
1.create the openshift-storage namespace
  oc create namespace openshift-storage

2.label the openshift-storage namespace
  oc label namespace openshift-storage "openshift.io/cluster-monitoring=true"

3.Go to the webconsole -> Operators -> OperatorHub

4.Search for "ocs" and install the operator in the openshift-storage namespace.


Actual results:

Status: Unknown
Operator not installed

Expected results:
Status: up to date
Operator installed

Comment 2 Valentino Uberti 2020-02-26 15:20:05 UTC

[root@bastion ocp4install_4.3]# oc describe sub ocs-operator
Name:         ocs-operator
Namespace:    openshift-storage
Labels:       <none>
Annotations:  <none>
API Version:  operators.coreos.com/v1alpha1
Kind:         Subscription
Metadata:
  Creation Timestamp:  2020-02-26T15:16:32Z
  Generation:          1
  Resource Version:    519538
  Self Link:           /apis/operators.coreos.com/v1alpha1/namespaces/openshift-storage/subscriptions/ocs-operator
  UID:                 e4b24dfd-df74-441e-ad04-5b881ad73dea
Spec:
  Channel:                stable-4.2
  Install Plan Approval:  Manual
  Name:                   ocs-operator
  Source:                 redhat-operators
  Source Namespace:       openshift-marketplace
  Starting CSV:           ocs-operator.v4.2.1
Status:
  Catalog Health:
    Catalog Source Ref:
      API Version:       operators.coreos.com/v1alpha1
      Kind:              CatalogSource
      Name:              certified-operators
      Namespace:         openshift-marketplace
      Resource Version:  518803
      UID:               9655052a-c6f8-43b0-8ac3-a743ae82c02e
    Healthy:             true
    Last Updated:        2020-02-26T15:16:32Z
    Catalog Source Ref:
      API Version:       operators.coreos.com/v1alpha1
      Kind:              CatalogSource
      Name:              community-operators
      Namespace:         openshift-marketplace
      Resource Version:  518798
      UID:               d0d0f96f-85ec-4a12-83be-eb95ddc1f9ff
    Healthy:             true
    Last Updated:        2020-02-26T15:16:32Z
    Catalog Source Ref:
      API Version:       operators.coreos.com/v1alpha1
      Kind:              CatalogSource
      Name:              redhat-operators
      Namespace:         openshift-marketplace
      Resource Version:  518813
      UID:               bd507019-ed9b-4ca6-a367-e80cdf8708cc
    Healthy:             true
    Last Updated:        2020-02-26T15:16:32Z
  Conditions:
    Last Transition Time:  2020-02-26T15:16:32Z
    Message:               all available catalogsources are healthy
    Reason:                AllCatalogSourcesHealthy
    Status:                False
    Type:                  CatalogSourcesUnhealthy
  Last Updated:            2020-02-26T15:16:32Z
Events:                    <none>

Comment 3 Jose A. Rivera 2020-02-27 16:47:14 UTC

This should be fixed now, please try again.

Comment 4 Valentino Uberti 2020-02-27 17:55:15 UTC

Hi Jose, thank you now it works. May i ask you how did you fix this issue?

Comment 5 Jose A. Rivera 2020-02-27 18:01:10 UTC

There was something of a global outage for one of our dependencies in the Operator Lifecycle Manager catalogs. It was a regression on our part and we reverted the offending change.

Comment 6 Valentino Uberti 2020-02-27 22:09:18 UTC

Thank you Jose