-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.22
-
None
-
None
-
False
-
-
None
-
None
-
None
-
ppc64le
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
PowerVS 4.22, is having the maximum test case failures and majority of them are PVC related.
Few example
: [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy should delete PVCs with a OnScaledown policy
: [sig-apps] StatefulSet Non-retain StatefulSetPersistentVolumeClaimPolicy should not delete PVC with OnScaledown policy if another controller owns the PVC
: [sig-storage] PVC Protection Verify that PVC in active use by a pod is not removed immediately
All of them are failing because they are unable to attach claimed volume to the Worker.
All of them have conflicts stating the volume is already in use, the log is a bit confusing.
Warning FailedAttachVolume 32s (x7 over 8m33s) attachdetach-controller AttachVolume.Attach failed for volume "pvc-b7cc1bdb-70b2-4b5a-b01d-b967284972ca" : rpc error: code = Internal desc = Could not attach volume "c276ed7d-a350-4ef6-9aa2-73727f426ced" to node "9e3518c1-8362-4e8d-aa89-895805c322a7": failed to perform the Attach volume Operation for volume c276ed7d-a350-4ef6-9aa2-73727f426ced with error [POST /pcloud/v1/cloud-instances/{cloud_instance_id}/pvm-instances/{pvm_instance_id}/volumes/{volume_id}][409] pcloudPvminstancesVolumesPostConflict {"description":"Conflict: volume c276ed7d-a350-4ef6-9aa2-73727f426ced attach to server p-fran-3-capi-422-z5htp-worker-l9fxc failed, volume has status 'in-use' and needs to be 'available', 'creating', or 'in-use' with multiattach enabled","error":"Conflict"}
Ref jobs: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.22-ocp-e2e-ovn-powervs-capi-multi-p-p/2018535254129643520
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.22-ocp-e2e-ovn-powervs-capi-multi-p-p/2019984747169583104
