Support Confirmation for2.14.2onK8s 1.32.3

Question

Topic: Container Storage Modules Title: [Qualification]: Support Confirmation for2.14.2onK8s 1.32.3Operating System: RHEL 9.2Container Orchestrator: KubernetessStorage Platform: PowerFlexProtocol: ScaleIO protocol Relevant Log Output:  Test Name v1.32 VolumeIO Suite O Scaling Suite O Volume Cloning Suite O Volume Expansion Suite O Volume Expansion with raw block volumes O Snapshot Suite & the Replication Suite O Multi-Attach Volume Suite with raw block volumes X The container image does not include blcokdev command  Multi-Attach Volume Suite (Storage Class must be NFS) X Block Storage, so all fail Volume Health Metrics Suite O Multi-Attach Volume Suite with the volume access mode RWOP O Ephemeral Volumes Suite O Storage Class Capacity Tracking Suite X error=storage class does not use late bindingThis customer is using immediate binding

karthikk1 · Accepted Answer

All the functionalities updated have been validated and are working as expected, except for the raw device feature, which is currently not supported in the configuration as stated. Since this is the only exception and the rest of the solution meets the required specifications, we kindly request your support in approving the RPQ (Request for Product Qualification) to proceed further.

anandrajak · Answer

Hi @koj6 - Kindly upload the log file(s) using the 'Drop files here or browse' option.

Note:When submitting logs, please ensure that all files are sanitized to remove any company-sensitive information, including credentials, IP addresses, hostnames, or proprietary data. This helps protect your organization’s privacy and ensures compliance with data handling best practices.

Each uploaded log file must not exceed 10 MB in size.

akshay_saini1 · Answer

Thank you for sharing the log. The review is currently in progress, and we will provide an update once the analysis is complete.

karthikk1 · Answer

We noticed that the Multi-Attach Volume Suite test for raw block volumes is failing, and it appears to be due to the container image not including the blockdev command. This utility is typically bundled with the driver image. To help us investigate further, could you please provide the following details: Which version of the CSI driver is currently installed? Driver logs from the controller pod using the command below: kubectl logs -c driver -n kubectl describe pods -n

karthikk1 · Answer

@koj6  Any Updates on above request?

koj6 · Answer

Hi Karthik, Since it's difficult to provide logs from the customer's environment, I'm providing the requested results from an identical setup in our lab for now. We appreciate your understanding. Also, the customer is not using RAW block devices and has no plans to use them in the future.

2 Attachments

describe_controller.txt

logs_controller.txt

koj6 · Answer

@karthikk1​ Many Thanks

Test Name	v1.32
VolumeIO Suite	O
Scaling Suite	O
Volume Cloning Suite	O
Volume Expansion Suite	O
Volume Expansion with raw block volumes	O
Snapshot Suite & the Replication Suite	O
Multi-Attach Volume Suite with raw block volumes	X	The container image does not include blcokdev command
Multi-Attach Volume Suite (Storage Class must be NFS)	X	Block Storage, so all fail
Volume Health Metrics Suite	O
Multi-Attach Volume Suite with the volume access mode RWOP	O
Ephemeral Volumes Suite	O
Storage Class Capacity Tracking Suite	X	error=storage class does not use late binding This customer is using immediate binding

Container Storage Modules

Support Confirmation for2.14.2onK8s 1.32.3

Was this post helpful?