ource Type VolumeSnapshot by Name new-snapshot-demo: snapshot new-snapshot-demo not bound I0714 08:37:27.829848 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"snapshot-demo-restore", UID:"8dd75b4b-9a16-4940-b078-7088a672a649", APIVersion:"v1", ResourceVersion:"2855605", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "evs-sc": error getting handle for DataSource Type VolumeSnapshot by Name new-snapshot-demo: snapshot new-snapshot-demo not bound I0714 08:38:13.719937 1 controller.go:1279] provision "default/snapshot-demo-restore" class "evs-sc": started I0714 08:38:13.720202 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"snapshot-demo-restore", UID:"8dd75b4b-9a16-4940-b078-7088a672a649", APIVersion:"v1", ResourceVersion:"2868531", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/snapshot-demo-restore" W0714 08:38:13.723506 1 controller.go:933] Retrying syncing claim "8dd75b4b-9a16-4940-b078-7088a672a649", failure 31 E0714 08:38:13.723534 1 controller.go:956] error syncing claim "8dd75b4b-9a16-4940-b078-7088a672a649": failed to provision volume with StorageClass "evs-sc": error getting handle for DataSource Type VolumeSnapshot by Name new-snapshot-demo: snapshot new-snapshot-demo not bound I0714 08:38:13.723562 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"snapshot-demo-restore", UID:"8dd75b4b-9a16-4940-b078-7088a672a649", APIVersion:"v1", ResourceVersion:"2868531", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "evs-sc": error getting handle for DataSource Type VolumeSnapshot by Name new-snapshot-demo: snapshot new-snapshot-demo not bound
时间: 2023-07-21 18:11:39 浏览: 256
根据提供的日志,出现了以下问题:“error getting handle for DataSource Type VolumeSnapshot by Name new-snapshot-demo: snapshot new-snapshot-demo not bound”。这表明在创建持久卷声明时,无法找到名为 "new-snapshot-demo" 的 VolumeSnapshot。
为了解决这个问题,您可以尝试以下几种方法:
1. 确保名为 "new-snapshot-demo" 的 VolumeSnapshot 存在,并且已正确绑定到相应的快照。您可以使用以下命令检查:
```
kubectl get volumesnapshot new-snapshot-demo
```
确保快照状态为 "Bound"。
2. 检查持久卷声明的配置文件中是否指定了正确的 VolumeSnapshot 名称。请确保在配置文件中的 `spec` 部分中使用了正确的名称。
3. 检查您是否具有足够的权限来访问 VolumeSnapshot。如果您没有足够的权限,可能无法找到或绑定 VolumeSnapshot。请联系集群管理员以获取更多权限。
4. 如果您刚刚创建了名为 "new-snapshot-demo" 的 VolumeSnapshot,请确保它已经完成绑定过程。绑定可能需要一些时间来完成。您可以使用以下命令检查绑定状态:
```
kubectl describe volumesnapshot new-snapshot-demo
```
检查事件或错误消息,以了解绑定过程是否成功完成。
如果问题仍然存在,请提供更多详细信息,例如 VolumeSnapshot 和持久卷声明的配置文件,以便我们能够更好地帮助您解决问题。
阅读全文