search

fluxcd / flux

Successor: https://github.com/fluxcd/flux2
https://fluxcd.io
Apache License 2.0
6.9k stars 1.08k forks source link

GCR content-type errors #879

Closed mithrandi closed 6 years ago

mithrandi commented 6 years ago

I'm seeing a lot of errors logged like this:

ts=2017-12-20T19:50:26.214459657Z caller=warming.go:148 component=warmer err="requesting manifests: getting remote manifest: Get https://gcr.io/v2/kubernetes-helm/tiller/manifests/v2.0.0: http: non-successful response (status=404 body=\"{\
\\"errors\\\":[{\\\"code\\\":\\\"MANIFEST_UNKNOWN\\\",\\\"message\\\":\\\"Manifest with tag 'v2.0.0' has media type 'application/vnd.docker.distribution.manifest.v1+prettyjws', but client accepts 'application/vnd.docker.distribution.manifest.v1+json'.\\\"}]}\")"

This is with Flux 1.1.0 as well as master. The images for the controller(s) in question show as "waiting for cache" forever, presumably due to this error.

squaremo commented 6 years ago

Thanks for posting this issue @mithrandi. We were also seeing these log messages, as reported in #838. It was fixed in #851, which made its way to master pretty recently, and will be in the next release (soon!).

squaremo commented 6 years ago

(closing as a duplicate of #838, but please do comment here, or file a further issue, if you still have problems that #851 is supposed to fix)

mithrandi commented 6 years ago

Aha! It looks like I was running the master revision just before that was merged, upgrading does resolve the issue as expected.