W0714 03:29:51.128705 1 controller.go:933] Retrying syncing claim "fd341a80-08e3-4dcc-a55d-805f06035a0f", failure 19 E0714 03:29:51.128728 1 controller.go:956] error syncing claim "fd341a80-08e3-4dcc-a55d-805f06035a0f": 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 03:29:51.128743 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"snapshot-demo-restore", UID:"fd341a80-08e3-4dcc-a55d-805f06035a0f", APIVersion:"v1", ResourceVersion:"2814762", 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 [root@master ~]# kubectl get volumesnapshot
时间: 2023-07-22 13:11:44 浏览: 74
根据您提供的日志信息,出现了一个错误消息:无法通过名称为`new-snapshot-demo`的VolumeSnapshot获取数据源类型的处理程序。这表明`new-snapshot-demo`快照未绑定。
另外,您还提到了一个警告事件:使用StorageClass "evs-sc"无法为PersistentVolumeClaim "snapshot-demo-restore"提供卷。这也是由于无法获取数据源类型为VolumeSnapshot且名称为`new-snapshot-demo`的处理程序。
最后,您提到了一个`kubectl get volumesnapshot`命令,但您没有提供完整的命令输出。如果您需要查询VolumeSnapshot,请确保输入正确的命令,并在需要时提供完整的命令输出和上下文信息。
相关问题
W0714 03:29:51.128705 1 controller.go:933] Retrying syncing claim "fd341a80-08e3-4dcc-a55d-805f06035a0f", failure 19 E0714 03:29:51.128728 1 controller.go:956] error syncing claim "fd341a80-08e3-4dcc-a55d-805f06035a0f": 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 03:29:51.128743 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"snapshot-demo-restore", UID:"fd341a80-08e3-4dcc-a55d-805f06035a0f", APIVersion:"v1", ResourceVersion:"2814762", 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
根据您提供的日志信息,出现了一个错误消息:无法通过名称为`new-snapshot-demo`的VolumeSnapshot获取数据源类型的处理程序。这表明`new-snapshot-demo`快照未绑定。
这个错误发生在尝试使用StorageClass为"evs-sc"为PersistentVolumeClaim "snapshot-demo-restore"提供卷时。由于无法获取名称为`new-snapshot-demo`的VolumeSnapshot的数据源类型处理程序,导致卷的提供失败。
您还提到了一个警告事件,指示卷的提供失败。该事件的详细信息与上述错误消息相同。
请检查您的VolumeSnapshot配置和绑定状态,确保`new-snapshot-demo`快照已正确绑定,并且StorageClass配置正确。如果问题仍然存在,请提供更多上下文信息以便进一步帮助您解决问题。
W0716 17:21:10.274940 1 controller.go:946] Retrying syncing claim "9741fa13-f40c-4680-a1aa-f0c3106937d8" because failures 2 < threshold 15 E0716 17:21:10.275002 1 controller.go:966] error syncing claim "9741fa13-f40c-4680-a1aa-f0c3106937d8": failed to provision volume with StorageClass "nfs": unable to create directory to provision new pv: mkdir /persistentvolumes/default-test-claim1-pvc-9741fa13-f40c-4680-a1aa-f0c3106937d8: read-only file system I0716 17:21:10.275042 1 event.go:278] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-claim1", UID:"9741fa13-f40c-4680-a1aa-f0c3106937d8", APIVersion:"v1", ResourceVersion:"1955978", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "nfs": unable to create directory to provision new pv: mkdir /persistentvolumes/default-test-claim1-pvc-9741fa13-f40c-4680-a1aa-f0c3106937d8: read-only file system
根据提供的事件日志,可以看到以下信息:
1. 警告日志:`Retrying syncing claim "9741fa13-f40c-4680-a1aa-f0c3106937d8" because failures 2 < threshold 15`,这表示持久卷控制器正在尝试重新同步声明,因为失败次数未达到阈值。
2. 错误日志:`error syncing claim "9741fa13-f40c-4680-a1aa-f0c3106937d8": failed to provision volume with StorageClass "nfs": unable to create directory to new pv: mkdir /persistentvolumes/default-test-claim1-pvc-9741fa1340c-4680-a1aa-f0c3106937d8: read-only file system`,这表示在使用 StorageClass "nfs" 提供卷时出现错误,无法创建目录 `/persistentvolumes/default-test-claim1-pvc-9741fa13-f40c-4680-a1aa-f0c3106937d8`,因为文件系统是只读的。
3. 事件日志:`Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-claim1", UID:"9741fa13-f40c-4680-a1aa-f0c3106937d8", APIVersion:"v1", ResourceVersion:"1955978", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "nfs": unable to create directory to provision new pv: mkdir /persistentvolumes/default-test-claim1-pvc-9741fa13-f40c-4680-a1aa-f0c3106937d8: read-only file system`,这是一个事件记录,指示卷的创建失败,原因是无法在 `/persistentvolumes/default-test-claim1-pvc-9741fa13-f40c-4680-a1aa-f0c3106937d8` 目录下创建目录,因为文件系统是只读的。
根据日志信息,问题可能是由于文件系统只读导致无法创建目录。请按照之前提到的文件系统只读问题的排查步骤进行检查,并确保文件系统的权限设置正确,并且没有其他组件或策略阻止了写操作。
如果问题仍然存在,请提供更多上下文或详细信息,以便更好地理解问题所在。