Bug 1882383 - oVirt CSI driver does not support xfs
Summary: oVirt CSI driver does not support xfs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.6.0
Assignee: Benny Zlotnik
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-24 12:38 UTC by Jan Safranek
Modified: 2020-10-27 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:45:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ovirt-csi-driver pull 47 0 None closed Bug 1882383: Support XFS 2021-02-10 07:39:21 UTC
Github openshift ovirt-csi-driver pull 50 0 None closed Bug 1882383: Add xfs utils to the driver image 2021-02-10 07:39:21 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:45:22 UTC

Description Jan Safranek 2020-09-24 12:38:24 UTC
RHV / oVirt CSI driver does not support provisioning of volumes with xfs filesystem.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. Create a storage class with oVirt + XFS filesystem, i.e. with:
parameters:
  csi.storage.k8s.io/fstype: xfs

2. Create a PVC that uses the storage class.
3. Run a pod with that PVC.

Actual results:
Pod won't start

Expected results:
Pod starts and the volume is formatted with xfs.

Comment 2 Guilherme Santos 2020-10-02 13:42:02 UTC
Failed on:
openshift-install-4.6.0-0.nightly-2020-10-02-065738

Steps:
1. Created a storage class (ovirt-csi-sc-xfs) with "csi.storage.k8s.io/fstype: xfs" parameter
2. Created a pvc in that storage class
# oc get pvc 
NAME               STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
1-ovirt-cow-disk   Bound    pvc-268b6d17-5b56-472e-a525-588afe61f81b   954Mi      RWO            ovirt-csi-sc-xfs   2m14s


3. Create a test pod in that uses the pvc:
# oc get pods
NAME             READY   STATUS              RESTARTS   AGE
testpodwithcsi   0/1     ContainerCreating   0          6m51s

# oc describe pod testpodwithcsi
...
Events:
  Type     Reason                  Age                    From                     Message
  ----     ------                  ----                   ----                     -------
  Normal   Scheduled               7m48s                  default-scheduler        Successfully assigned default/testpodwithcsi to primary-8hhkw-worker-0-6kqwn
  Warning  FailedAttachVolume      7m32s (x6 over 7m48s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-268b6d17-5b56-472e-a525-588afe61f81b" : rpc error: code = Unknown desc = Fault reason is "Operation Failed". Fault detail is "[Cannot attach Virtual Disk: The following disks are locked: pvc-268b6d17-5b56-472e-a525-588afe61f81b. Please try again in a few minutes.]". HTTP response code is "409". HTTP response message is "409 Conflict".
  Normal   SuccessfulAttachVolume  7m15s                  attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-268b6d17-5b56-472e-a525-588afe61f81b"
  Warning  FailedMount             5m45s                  kubelet                  Unable to attach or mount volumes: unmounted volumes=[pv0002], unattached volumes=[default-token-kpwvs pv0002]: timed out waiting for the condition
  Warning  FailedMount             72s (x2 over 3m29s)    kubelet                  Unable to attach or mount volumes: unmounted volumes=[pv0002], unattached volumes=[pv0002 default-token-kpwvs]: timed out waiting for the condition
  Warning  FailedMount             24s (x11 over 6m38s)   kubelet                  MountVolume.MountDevice failed for volume "pvc-268b6d17-5b56-472e-a525-588afe61f81b" : rpc error: code = Unknown desc = exit status 1 mkfs failed with exit status 1


Results:
storage create but mkfs issue persists

Comment 3 Jan Safranek 2020-10-02 15:56:06 UTC
I don't see mkfs.xfs in today's build of ovirt-csi-driver (4.6.0-0.nightly-2020-10-02-113823, quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d60bb76ae1df5c293b2f689d45a67041aa17e12d97974c7a42552f76a5bbf9b1)

Comment 5 Guilherme Santos 2020-10-05 12:41:51 UTC
Verified on:
openshift-4.6.0-0.nightly-2020-10-03-051134

Steps:
sames as the ones on comment #2

Results:
# oc get pods
NAME             READY   STATUS    RESTARTS   AGE
testpodwithcsixfs   1/1     Running   0          33s

storage created and pod running on it with xfs as expected

Comment 8 errata-xmlrpc 2020-10-27 16:45:08 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196


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