Test Scenarios for Suse SLES12SP3 custom filesystem paramters

Test Setup

• create a SLES12SP3 cluster
• keep all 4 deployments around till the end of the test

Testing ext4 without custom fs params

• create a volume + pv + pvc with filesystem ext4 named ext-ck-fail
• create a deployment that uses ext-ck-fail
• verify MountVolume.SetUp failed for volume "ext4-ck-fails" is part of the pod events
• verify that the pod does not enter running state

Testing ext4 with custom fs params1 (no 64bit, no metadata_csum)

• set the following filesystem parameters: -O ^64bit,^metadata_csum
• create a volume + pv + pvc with filesystem ext4 named ext4-no-ck-no-64
• create a deployment that uses ext4-no-ck-no-64
• verify that the pod enters running state and the volume is accessible

Testing ext4 with custom fs params2 (no metadata_csum)

• set the following filesystem parameters: -O ^metadata_csum
• create a volume + pv + pvc with filesystem ext4 named ext4-no-ck
• create a deployment that uses ext4-no-ck
• verify that the pod enters running state and the volume is accessible

Testing xfs after custom fs params (xfs should ignore the custom fs params)

• create a volume + pv + pvc with filesystem xfs named xfs-ignores
• create a deployment that uses xfs-ignores
• verify that the pod enters running state and the volume is accessible