白眉大叔 elero create restore --from-backup his
An error occurred: backups.velero.io "his" not found
这个时候，我去运行备份 也会报错
velero create backup devops-his --include-namespaces devops-his
查日志：
velero backup logs devops-his发现报错：
<Error><Code>AccessDenied</Code><Message>Request is not valid yet</Message><Key>backups/devops-his/devops-his-logs.gz</Key><BucketName>velero</BucketName><Resource>/velero/backups/devops-his/devops-his-logs.gz</Resource><RequestId>179A85EAC5F39461</RequestId><HostId>dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8</HostId></Error>
应该是权限的问题， 但是我不知道哪里权限不对， 同样的用户名密码，
在其他集群就可以访问， 在这里就访问不了。
查看 velero安装日志：
kubectl logs deployment/velero -n velero
level=error msg="Current backup storage locations available/unavailable/unknown: 0/1/0, Backup storage location \"default\" is unavailable: rpc error
在容器中查看日志：
level=error msg="Error listing backups in backup store" backupLocation=default controller=backup-sync error="rpc error: code = Unknown desc = RequestTimeTooSkewed: The difference between the request time and the server's time is too large.\n\tstatus code: 403, request id: 179A98C9F3E0ED75, host id: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8" error.file="/go/src/velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:361" error.function="main.(*ObjectStore).ListCommonPrefixes" logSource="pkg/controller/backup_sync_controller.go:182"
time="2023-11-24T23:30:31Z" level=error msg="Error listing backups in backup store" backupLocation=default controller=backup-sync error="rpc error: code = Unknown desc = RequestTimeTooSkewed: The difference between the request time and the server's time is too large.\n\tstatus code: 403, request id: 179A98D0F7FF88BC, host id: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8" error.file="/go/src/velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:361" error.function="main.(*ObjectStore).ListCommonPrefixes" logSource="pkg/controller/backup_sync_controller.go:182"有类似 主机时间不同步的问题。
The difference between the request time and the server's time is too large.
那么我们检查一下
改过后也没生效
发现主机的时间
[root@master1 ~]#
[root@master1 ~]# date
Sat Nov 25 07:38:50 CST 2023
而实际时间是
[root@master1 velero]# date
Fri Nov 24 11:40:02 PM CST 2023
[root@master1 velero]#
主机没有做时间同步， 我的问题。
后来重启了虚拟机， 然后就起不来了， 到了明天又自动恢复了， 教训，定期做etcd的备份。
欢迎来撩 ： 汇总all
