Bug 2111955

Summary: OCS OSD Deployer is in Installing phase after upgrade for 2 days on provider
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Filip Balák <fbalak>
Component: odf-managed-serviceAssignee: Ohad <omitrani>
Status: CLOSED CURRENTRELEASE QA Contact: Filip Balák <fbalak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11CC: aeyal, dbindra, lgangava, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.0.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-02 05:19:50 UTC 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 Filip Balák 2022-07-28 14:05:12 UTC
Description of problem:
After performing upgrade, ocs-osd-deployer.v2.0.4 is in installing state. This is observed on Provider cluster. On Consumers it is installed. On another (privatelink) provider it is installed.

$ oc get csv -n openshift-storage
NAME                                      DISPLAY                       VERSION           REPLACES                                  PHASE
mcg-operator.v4.10.5                      NooBaa Operator               4.10.5            mcg-operator.v4.10.4                      Succeeded
ocs-operator.v4.10.4                      OpenShift Container Storage   4.10.4            ocs-operator.v4.10.3                      Succeeded
ocs-osd-deployer.v2.0.4                   OCS OSD Deployer              2.0.4             ocs-osd-deployer.v2.0.3                   Installing
odf-csi-addons-operator.v4.10.4           CSI Addons                    4.10.4            odf-csi-addons-operator.v4.10.3           Succeeded
odf-operator.v4.10.4                      OpenShift Data Foundation     4.10.4            odf-operator.v4.10.3                      Succeeded
ose-prometheus-operator.4.10.0            Prometheus Operator           4.10.0            ose-prometheus-operator.4.8.0             Succeeded
route-monitor-operator.v0.1.422-151be96   Route Monitor Operator        0.1.422-151be96   route-monitor-operator.v0.1.420-b65f47e   Succeeded


How reproducible:
1/1

Steps to Reproduce:
1. Create Provider with 2 Consumers.
2. Upgrade addon to ocs-osd-deployer.v2.0.4
3. Wait for a long time

Actual results:
Addon is still installing.

Expected results:
Addon should be installed in a reasonable time.

Additional info:

Comment 1 Filip Balák 2022-07-28 14:42:09 UTC
As discussed in https://chat.google.com/room/AAAASHA9vWs/5OakFiBxlH0:
This was caused by an issue in ocm (missing ocs-provider-qe-prom-remote-write secret): https://app.slack.com/client/T027F3GAJ/C01L46M0FQC/thread/C01L46M0FQC-1658934690.637499
Freshly deployed clusters are working.

Comment 4 Leela Venkaiah Gangavarapu 2022-08-29 06:57:52 UTC
@fbalak,

- based on https://bugzilla.redhat.com/show_bug.cgi?id=2111955#c1, can this bug be closed?

thanks,
leela.

Comment 5 Dhruv Bindra 2022-09-05 11:16:28 UTC
Moving to ON_QA as it was fixed and works on fresh deployment

Comment 6 Filip Balák 2022-09-19 10:11:50 UTC
Original problem is resolved. --> VERIFIED

Tested with:
ocs-osd-deployer.v2.0.6