Bug 2101871

Summary:	RBD StorageClassClaim in Failed phase right after creation if ocs-operator restarted
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Filip Balák <fbalak>
Component:	odf-managed-service	Assignee:	Kaustav Majumder <kmajumde>
Status:	ASSIGNED ---	QA Contact:	Jilju Joy <jijoy>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	aeyal, dbindra, jijoy, nberry, odf-bz-bot
Target Milestone:	---	Keywords:	TestBlocker, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2101877 (view as bug list)		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:
Bug Depends On:
Bug Blocks:	2101877

Description Filip Balák 2022-06-28 15:07:48 UTC

Description of problem:
As discussed in https://chat.google.com/room/AAAASHA9vWs/8BJgltoxETc, if rbd storageclassclaim is created after ocs-operator restart then it ends in Failed phase.

Version-Release number of selected component (if applicable):
ocs-operator.v4.11.0

How reproducible:
1/1

Steps to Reproduce:
1. Install ODF Managed Service with ODF 4.11.
2. Create storageclassclaim
3. Restart ocs-operator
4. Create rbd storageclassclaim like:

apiVersion: ocs.openshift.io/v1alpha1
kind: StorageClassClaim
metadata:
  name: test-storageclassclaim
spec:
  # type: blockpool or sharedfilesystem
  type: blockpool

Actual results:
StorageClassClaims get into Failed state. In my case even the first claim went into failed phase. According to https://chat.google.com/room/AAAASHA9vWs/8BJgltoxETc we can follow steps in Reproducer for more confidence.

Expected results:
StorageClassClaims are ready.

Additional info:

Comment 4 Ohad 2022-08-23 17:22:29 UTC

@mrajanna Can you please answer the question?