Open zj452008181 opened 1 year ago
failed to authorize: failed to fetch oauth token: unable to decode token response: invalid character 'U' looking for beginning of value
It seems to have something to do with authorize.
Can you login to this registry directly by using docker login harbor.jusda.int
?
yes,i think there is some error in the artifact package,sometimes the images index.json file type was wrong,some keys were lost;and i treid run "kk create manifest manytimes",at finnal it success.
What is version of KubeKey has the issue?
3.0.2,3.0.7
What is your os environment?
centos 7.9
KubeKey config file
A clear and concise description of what happend.
14:20:47 CST success: [LocalHost] 14:20:47 CST [CopyImagesToRegistryModule] Push multi-arch manifest to private registry 14:20:47 CST Push multi-arch manifest list: harbor.jusda.int/kubesphere/ks-apiserver:v3.3.1 INFO[0154] Retrieving digests of member images
INFO[0154] trying next host error="failed to authorize: failed to fetch oauth token: unable to decode token response: invalid character 'U' looking for beginning of value" host=harbor.jusda.int 14:20:47 CST message: [LocalHost] push image harbor.jusda.int/kubesphere/ks-apiserver:v3.3.1 multi-arch manifest failed: Inspect of image "harbor.jusda.int/kubesphere/ks-apiserver:v3.3.1-amd64" failed with error: failed to authorize: failed to fetch oauth token: unable to decode token response: invalid character 'U' looking for beginning of value 14:20:47 CST failed: [LocalHost] error: Pipeline[CreateClusterPipeline] execute failed: Module[CopyImagesToRegistryModule] exec failed: failed: [LocalHost] [PushManifest] exec failed after 1 retires: push image harbor.jusda.int/kubesphere/ks-apiserver:v3.3.1 multi-arch manifest failed: Inspect of image "harbor.jusda.int/kubesphere/ks-apiserver:v3.3.1-amd64" failed with error: failed to authorize: failed to fetch oauth token: unable to decode token response: invalid character 'U' looking for beginning of value
Relevant log output
No response
Additional information
No response