From release-4.6 to the latest product version, a limitation related to the deployment of baremetal workers should be noted to the user (For example on [1]).

Due to ironic limitation, it is not possible to attach cinder volumes to the Baremetal workers after OS has started on the node. Ironic do not have any way of letting the operating system know of the new volume since it would be a security layer violation for the system to have detailed and privileged access to the workload.

As a result, creating a Pod with a PVC associated is leaving the pod in 'ContainerCreating' status forever:

$ oc get pods,pvc
NAME READY STATUS RESTARTS AGE
pod/demo-0-6f84fcd788-2ngtk 0/1 ContainerCreating 0 4h2m

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
persistentvolumeclaim/pvc-0 Bound pvc-1b6339d2-b075-4ecb-88d3-9aa243c98e87 1Gi RWO standard-csi 4h2m

And below error can be observed on nova logs:

2022-07-06 10:39:55.946 7 ERROR nova.virt.block_device [req-133c29d9-5c85-4986-93cb-d0f569414876 f371d33823304ab4a1d4d929c0691366 14c0bdfd2fcc4cb7981b90c7bd5c1a72 - default default] [instance: e57d07be-86db-463b-86c3-1ccbe3c9214b] Driver failed to attach volume 5ad7fbaa-99cc-4c8e-9c33-ac6b458188bb at /dev/sdb: NotImplementedError

[1]https://github.com/openshift/installer/blob/master/docs/user/openstack/deploy_baremetal_workers.md