external-snapshotter: cannot update snapshot metadata

My attempt of creating a new VolumeSnapshot from a PVC source resulted in following error message in external-snapshotter:

I0717 18:09:11.377904       1 connection.go:180] GRPC call: /csi.v1.Controller/CreateSnapshot
I0717 18:09:11.377925       1 connection.go:181] GRPC request: {"name":"snapshot-bd0540a0-1912-44f8-a04c-2e69ab1c21c6","secrets":"***stripped***","source_volume_id":"b44ffa38-5d65-4346-9265-807d9c966d6f"}
I0717 18:09:11.439795       1 reflector.go:235] github.com/kubernetes-csi/external-snapshotter/pkg/client/informers/externalversions/factory.go:117: forcing resync
I0717 18:09:11.577934       1 connection.go:183] GRPC response: {"snapshot":{"creation_time":{"seconds":1560416046},"ready_to_use":true,"size_bytes":1073741824,"snapshot_id":"bfe22f76-c3af-48a8-a326-6fdc3e5a747d","source_volume_id":"b44ffa38-5d65-4346-9265-807d9c966d6f"}}
I0717 18:09:11.579576       1 connection.go:184] GRPC error: <nil>
I0717 18:09:11.584450       1 snapshotter.go:81] CSI CreateSnapshot: snapshot-bd0540a0-1912-44f8-a04c-2e69ab1c21c6 driver name [nfs.manila.csi.openstack.org] snapshot ID [bfe22f76-c3af-48a8-a326-6fdc3e5a747d] time stamp [&{1560416046 0 {} [] 0}] size [1073741824] readyToUse [true]
I0717 18:09:11.584530       1 snapshot_controller.go:640] Created snapshot: driver nfs.manila.csi.openstack.org, snapshotId bfe22f76-c3af-48a8-a326-6fdc3e5a747d, creationTime 2019-06-13 08:54:06 +0000 UTC, size 1073741824, readyToUse true
I0717 18:09:11.584563       1 snapshot_controller.go:645] createSnapshot [default/new-nfs-share-snap]: trying to update snapshot creation timestamp
I0717 18:09:11.584604       1 snapshot_controller.go:825] updating VolumeSnapshot[]default/new-nfs-share-snap, readyToUse true, timestamp 2019-06-13 08:54:06 +0000 UTC
I0717 18:09:11.588727       1 snapshot_controller.go:650] failed to update snapshot default/new-nfs-share-snap creation timestamp: snapshot controller failed to update default/new-nfs-share-snap on API server: the server could not find the requested resource (put volumesnapshots.snapshot.storage.k8s.io new-nfs-share-snap)

The snapshot is successfully created by the driver, but external-snapshotter is having trouble updating the snapshot object metadata.

I’m using external-snapshotter v1.2.0-0-gb3f591d8 in k8s 1.15.0 running with VolumeSnapshotDataSource=true feature gate. The previous version of external-snapshotter, 1.1.0, works just fine though. Is this a regression or rather mis-configuration on my part? Always happy to debug more or provide more logs! Thanks!

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 22 (5 by maintainers)

Commits related to this issue

Squashed 'release-tools/' changes from bc0504ad..c0a4fb1d c0a4fb1d Merge pull request #164 from anubha-v-ardhan/patch-1 9c6a6c08 Master to main cleanup 682c686a Merge pull request #162 from pohly/pod... — committed to xing-yang/external-snapshotter by xing-yang 3 years ago
Merge pull request #147 from pohly/mock-testing Mock testing — committed to xing-yang/external-snapshotter by k8s-ci-robot 3 years ago

Most upvoted comments

@gman0 @xing-yang I have tested it in v1.15.0, I have already installed snapshot( image’s version is v1.0.1) CRD v1.0.1 in my k8s cluster and successful snapshot creation, but when I upgrade the image’s version to v1.2.0, the CRD will not be upgraded, it used old CRD, so I delete the snapshot pod and old CRD and rebuild snapshot pod, It can works.

It’s no needed to restart k8s cluster, only delete the crd.

@xing-yang Maybe we should delete the old CRD when creating snapshot pod that if the CRD version is different with the image’s version?

zhucan on Jul 22, 2019