Bug 2101871 - RBD StorageClassClaim in Failed phase right after creation if ocs-operator restarted
Summary: RBD StorageClassClaim in Failed phase right after creation if ocs-operator re...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Kaustav Majumder
QA Contact: Jilju Joy
URL:
Whiteboard:
Depends On:
Blocks: 2101877
TreeView+ depends on / blocked
 
Reported: 2022-06-28 15:07 UTC by Filip Balák
Modified: 2023-08-09 17:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2101877 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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?


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