harbor 1.8.0-rc1 oss registry unhealthy aliyun api error #7820
Comments
|
hi @Ethan-2017 the error message seems that your accesskeyid or accesskeysecret is not correct |
|
@ywk253100 I'M sure this accesskeyid or accesskeysecret is correct 。 |
|
when I add the bucket name to the endpoint ,the registry is health ,but chart is not health |
|
I want to both registry and chart running at the same time in using aliyun oss。 |
|
#7750 is merged and will be cherry picked into 1.8 branch. You can try the 1.8 RC2 build later. |
|
@ywk253100 Today I install the versions of 1.8 RC2 ,the same error happening? the chart is ok and it can push chart to the helmcharts ,but cannot push the image to the registry in the same time . |
|
@Ethan-2017 what is the error message in the registry? |
|
@ninjadq May 16 13:43:34 172.18.0.1 registry[550]: 2019/05/16 05:43:34 GET https://oss-cn-zhangjiakou-internal.aliyuncs.com/?delimiter=&marker=&max-keys=1&prefix= ... |
|
May 17 13:57:53 172.21.0.1 registry[11279]: |
@Ethan-2017 You need to set the endpoint prefixed by your bucket name in harbor.cfg, then #7750 will make sure your chart is ok. |
|
@liqiang-fit2cloud when I set the endpoint prefixed by my bucket name in harbor.yml ,both chart and registry is ok 。 thank you everybody ! |
Versions:
Please specify the versions of following systems.
Additional context:
harbor.cfgand files in the samestorage_service:
oss:
accesskeyid: XXXXXXXXXXXX
accesskeysecret: XXXXXXXXXXXX
region: oss-cn-zhangjiakou
endpoint: oss-cn-zhangjiakou-internal.aliyuncs.com
bucket: xxxxxxxxxxxx
internal: true
ca_bundle: /etc/ssl/certs/
directory, including subdirectory.
/var/log/harbor/./api/healthy
{
"status": "unhealthy",
"components": [
{
"name": "database",
"status": "healthy"
},
{
"name": "redis",
"status": "healthy"
},
{
"name": "chartmuseum",
"status": "healthy"
},
{
"name": "clair",
"status": "healthy"
},
{
"name": "core",
"status": "healthy"
},
{
"name": "portal",
"status": "healthy"
},
{
"name": "registryctl",
"status": "healthy"
},
{
"name": "jobservice",
"status": "healthy"
},
{
"name": "registry",
"status": "unhealthy",
"error": "failed to check health: Get http://registry:5000/v2: dial tcp: lookup registry: no such host"
}
]
}
/var/lib/harbor/
May 16 13:42:33 172.18.0.1 registry[550]:
May 16 13:42:33 172.18.0.1 registry[550]: goroutine 1 [running]:
May 16 13:42:33 172.18.0.1 registry[550]: github.com/docker/distribution/registry/handlers.NewApp(0xff4ac0, 0xc000430300, 0xc0003e8a80, 0x0)
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/registry/handlers/app.go:126 +0x2fbb
May 16 13:42:33 172.18.0.1 registry[550]: github.com/docker/distribution/registry.NewRegistry(0xff4ac0, 0xc000430300, 0xc0003e8a80, 0xe, 0x0, 0x0)
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/registry/registry.go:105 +0x1dc
May 16 13:42:33 172.18.0.1 registry[550]: github.com/docker/distribution/registry.glob..func1(0x171ee40, 0xc000404170, 0x1, 0x1)
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/registry/registry.go:63 +0x187
May 16 13:42:33 172.18.0.1 registry[550]: github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).execute(0x171ee40, 0xc000404130, 0x1, 0x1, 0x171ee40, 0xc000404130)
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:495 +0x191
May 16 13:42:33 172.18.0.1 registry[550]: github.com/docker/distribution/vendor/github.com/spf13/cobra.(*Command).Execute(0x171efe0, 0xc0001c1f88, 0xc00007a058)
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/vendor/github.com/spf13/cobra/command.go:560 +0x2f4
May 16 13:42:33 172.18.0.1 registry[550]: main.main()
May 16 13:42:33 172.18.0.1 registry[550]: #11/go/src/github.com/docker/distribution/cmd/registry/main.go:23 +0x2d
May 16 13:43:34 172.18.0.1 registry[550]: time="2019-05-16T05:43:34.281332578Z" level=info msg="debug server listening localhost:5001"
May 16 13:43:34 172.18.0.1 registry[550]: 2019/05/16 05:43:34 GET https://oss-cn-zhangjiakou-internal.aliyuncs.com/?delimiter=&marker=&max-keys=1&prefix= ...
May 16 13:43:34 172.18.0.1 registry[550]: panic: Aliyun API Error: RequestId: 5CDCF88686XXXXXXX Status Code: 403 Code: SignatureDoesNotMatch Message: The request signature we calculated does not match the signature you provided. Check your key and signing method.
this error cause harbor canot login and push the images to registry
The text was updated successfully, but these errors were encountered: