-
Notifications
You must be signed in to change notification settings - Fork 404
Closed
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Description
What happened:
Create snapshot content X with volumeSnapshotRef field and namespace: one . Create snapshot Y with namespace two. Error outputs Failed to check and update snapshot: VolumeSnapshotContent [X] is bound to a different snapshot
What you expected to happen:
A different error message such as "Snapshot not found"
How to reproduce it:
X snapshot content:
apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshotContent
metadata:
name: "content"
namespace: "one"
spec:
deletionPolicy: Retain
driver: ebs.csi.aws.com
source:
snapshotHandle: "aws_handle"
volumeSnapshotRef:
name: "snapshot"
namespace: "one"
Y Snapshot:
apiVersion: snapshot.storage.k8s.io/v1
kind: VolumeSnapshot
metadata:
name: "snapshot"
namespace: "two"
spec:
source:
volumeSnapshotContentName: "content"
Anything else we need to know?:
Environment:
- Driver version: 5.0.1
- Kubernetes version (use
kubectl version): 1.21
Metadata
Metadata
Assignees
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.