Bug 1994588 - CSI drivers are not getting created when installing OCS 4.8 on top of OCP 4.9
Summary: CSI drivers are not getting created when installing OCS 4.8 on top of OCP 4.9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: rook
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.8.2
Assignee: Yug Gupta
QA Contact: Petr Balogh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-17 13:15 UTC by Petr Balogh
Modified: 2021-09-29 15:03 UTC (History)
4 users (show)

Fixed In Version: v4.8.2-179.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-29 15:03:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift rook pull 282 0 None None None 2021-08-18 08:36:58 UTC
Github openshift rook pull 287 0 None None None 2021-08-31 12:43:40 UTC
Github rook rook pull 8029 0 None None None 2021-08-17 13:28:44 UTC
Github rook rook pull 8582 0 None None None 2021-08-25 08:09:47 UTC
Red Hat Product Errata RHBA-2021:3695 0 None None None 2021-09-29 15:03:39 UTC

Description Petr Balogh 2021-08-17 13:15:54 UTC
Description of problem (please be detailed as possible and provide log
snippests):

After installation of OCS we see only this CSI drivers:
NAME              ATTACHREQUIRED   PODINFOONMOUNT   STORAGECAPACITY   TOKENREQUESTS   REQUIRESREPUBLISH   MODES        AGE
ebs.csi.aws.com   true             false            false             <unset>         false               Persistent   103m

But we are suppose to have also: ['openshift-storage.cephfs.csi.ceph.com', 'openshift-storage.rbd.csi.ceph.com']

Based on conversation in this thread:

https://chat.google.com/room/AAAAREGEba8/6Ldd2iWj6bk

And similar bug on 4.9: https://bugzilla.redhat.com/show_bug.cgi?id=1993918

We will want to fix and backport the fix to 4.8.2 z-stream.


Version of all relevant components (if applicable):
OCS 4.8.0
OCP 4.9 nightly


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?


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


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. Install OCP 4.9
2. Install OCS 4.8
3.


Actual results:
No CSI drivers created

Expected results:
['openshift-storage.cephfs.csi.ceph.com', 'openshift-storage.rbd.csi.ceph.com']
Have those CSI drivers created

Additional info:

Job:
https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/1641/
Logs:
http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-060ai3c33-ua/j-060ai3c33-ua_20210817T101227/logs/failed_testcase_ocs_logs_1629196655/test_deployment_ocs_logs/

Comment 5 Yug Gupta 2021-08-18 08:35:28 UTC
Sent the PR for backporting https://github.com/openshift/rook/pull/282

Comment 7 Mudit Agarwal 2021-08-31 12:39:01 UTC
Moving back to POST as we still need to backport https://github.com/rook/rook/pull/8582

Comment 8 Yug Gupta 2021-08-31 12:45:38 UTC
The second PR to be backported is also up https://github.com/openshift/rook/pull/282

Comment 12 Petr Balogh 2021-09-02 10:40:26 UTC
Based on execution above marking as verified as I see the deployment:
PASSED [100%]

Comment 18 errata-xmlrpc 2021-09-29 15:03:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Container Storage 4.8.2 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:3695


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