Invalid Volume, No retries permitted during Compliance Operator rescan in OCP
Issue
- A Compliance Scan was run successfully.
- When re-running the same compliance scan, there is an error:
stderr F E0825 02:59:36.414908 1 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/csi/ebs.csi.aws.com^vol-07fba6d7195dd656a podName: nodeName:}" failed. No retries permitted until 2025-08-25 03:01:38.414892212 +0000 UTC m=+3574090.425235539 (durationBeforeRetry 2m2s). Error: AttachVolume.Attach failed for volume "pvc-f5cb6b84-33a9-4c1e-b5da-09fbe04f54aa" (UniqueName: "kubernetes.io/csi/ebs.csi.aws.com^vol-07fba6d7195dd656a") from node "ip-10-131-132-152.ec2.internal" : rpc error: code = Internal desc = Could not attach volume "vol-07fba6d7195dd656a" to node "i-0b16a760228ec060f": could not attach volume "vol-07fba6d7195dd656a" to node "i-0b16a760228ec060f": operation error EC2: AttachVolume, https response error StatusCode: 400, RequestID: e7298421-46b1-41f7-b3ce-494b9d20f622, api error InvalidVolume.NotFound: The volume 'vol-07fba6d7195dd656a' does not exist.
Environment
- OpenShift Container Platform
- 4.x
- Compliance Operator
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.