Attempts to delete a VolumeSnapshotContent continually fail

[sventi555]

I tried to create a VolumeSnapshotContent that references a pre-existing snapshot in DigitalOcean. I then specify that VolumeSnapshotContent resource as a source in a VolumeSnapshot.

When I subsequently tried to delete both resources, the VolumeSnapshotContent did not delete (after being marked for deletion for over 10 minutes).

Here are the resource manifests:

apiVersion: snapshot.storage.k8s.io/v1beta1
kind: VolumeSnapshotContent
metadata:
  name: corner-mongo-snapshot-content
  namespace: corner
spec:
  deletionPolicy: Retain
  driver: hostpath.csi.k8s.io
  source:
    snapshotHandle: f2f3056c-01c8-11eb-9792-0a58ac14e18c
  volumeSnapshotRef:
    name: corner-mongo-snapshot
    namespace: corner

apiVersion: snapshot.storage.k8s.io/v1beta1
kind: VolumeSnapshot
metadata:
  name: corner-mongo-snapshot
  namespace: corner
spec:
  source:
    volumeSnapshotContentName: corner-mongo-snapshot-content

The snapshot indicated in the snapshotHandle exists on my DigitalOcean account.

Thank you!!

[pohly]

Hmm, what does this have to do with the csi-driver-host-path? 🤔

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.