Issue with cluster-level resources

Question

Issue with cluster-level resources

Closed this issue 5 years ago · 4 comments

I've been seeing this issue a lot lately:

ts=2019-03-19T18:15:52.144930335Z caller=loop.go:412 component=sync-loop err="executing HTTP request: 400 Bad Request parsing <cluster>:clusterrole/kube2iam: invalid service ID\n"

It causes fluxctl sync to return Error: timeout, but no other discernible issues.

Answer 1 · 2019-03-21T14:50:45.000Z

Are you using Weave Cloud (or fluxcloud)? I ask because this looks like it's a problem with the events the fluxd posts -- basically, that it constructs events that the receiver can't process.

Answer 2 · 2019-03-21T15:23:27.000Z

We are seeing this in our own infrastructure too.

Answer 3 · 2019-03-21T15:26:27.000Z

I am using fluxcloud. I was able to fix it by updating the flux-sync tag to the latest commit.

Answer 4 · 2019-03-22T16:09:57.000Z

@rcohenDBRS I think this should be fixed by #1851