The volumesnapshot’s status.readyToUse remains false and never gets set to true.

MichaelCade commented 11 months ago

What Happened?

Create a volume snapshot of a PVC.
Use the snapshotHandle(from volumesnapshotcontent) to create a new volumesnapshotcontent and volumesnapshot.
The volumesnapshot’s status.readyToUse remains false and never gets set to true.

Attach the log file

In snapshot-controller pods, continuos logs are as follows:

snapshot-controller-7564cc9b9-ls4c9 volume-snapshot-controller I1211 11:48:42.137430       1 leaderelection.go:352] lock is held by snapshot-controller-7564cc9b9-6cbhl and has not yet expired
snapshot-controller-7564cc9b9-ls4c9 volume-snapshot-controller I1211 11:48:42.137442       1 leaderelection.go:253] failed to acquire lease kube-system/snapshot-controller-leader
snapshot-controller-7564cc9b9-6cbhl volume-snapshot-controller I1211 11:48:44.475425       1 leaderelection.go:278] successfully renewed lease kube-system/snapshot-controller-leader
snapshot-controller-7564cc9b9-6cbhl volume-snapshot-controller I1211 11:48:49.491540       1 leaderelection.go:278] successfully renewed lease kube-system/snapshot-controller-leader
snapshot-controller-7564cc9b9-ls4c9 volume-snapshot-controller I1211 11:48:49.834635       1 leaderelection.go:352] lock is held by snapshot-controller-7564cc9b9-6cbhl and has not yet expired
snapshot-controller-7564cc9b9-ls4c9 volume-snapshot-controller I1211 11:48:49.834654       1 leaderelection.go:253] failed to acquire lease kube-system/snapshot-controller-leader

$ minikube version
minikube version: v1.32.0
commit: 8220a6eb95f0a4d75f7f2d7b14cef975f050512d

Operating System

None

Driver

None

MichaelCade commented 10 months ago

I am investigating the version installed via the minikube addon vs manually deploying the csi hostpath to see if this is the issue.

MichaelCade commented 10 months ago

I have just tested with a manual install of the external snapshotter and csi-driver-hostpath and this works with the process above.

git clone https://github.com/kubernetes-csi/external-snapshotter.git

cd external-snapshotter/

kubectl kustomize client/config/crd | kubectl create -f -

kubectl -n kube-system kustomize deploy/kubernetes/snapshot-controller | kubectl create -f -

cd ..

git clone https://github.com/kubernetes-csi/csi-driver-host-path.git

cd csi-driver-host-path/

./deploy/kubernetes-latest/deploy.sh

kubectl create -f  ./examples/csi-storageclass.yaml

Flagging as this seems to be an issue with the addons within minikube

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/17767#issuecomment-2153340967): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

k8s-ci-robot commented 4 months ago

@galvarado: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes/minikube/issues/17767#issuecomment-2224119895): >/reopen > >Just wanted to flag this again as I just hitted the above issue mentioned by @MichaelCade Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

galvarado commented 4 months ago

/remove-lifecycle rotten

Just wanted to flag this again as I just hitted the above issue mentioned by @MichaelCade

k8s-ci-robot commented 4 months ago

@galvarado: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes/minikube/issues/17767#issuecomment-2224120460): >/remove-lifecycle rotten > > >/reopen > >Just wanted to flag this again as I just hitted the above issue mentioned by @MichaelCade > > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

kubernetes / minikube