Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Issue with cluster-level resources #1843

Closed
rcohenDBRS opened this issue Mar 19, 2019 · 4 comments
Closed

Issue with cluster-level resources #1843

rcohenDBRS opened this issue Mar 19, 2019 · 4 comments
Assignees
@squaremo
Labels
bug dogfood

Comments

@rcohenDBRS
Copy link

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.
@squaremo squaremo added the bug label Mar 20, 2019
@squaremo
Copy link
Member

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.

@squaremo squaremo self-assigned this Mar 21, 2019
@squaremo
Copy link
Member

We are seeing this in our own infrastructure too.

@rcohenDBRS
Copy link
Author

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

@rcohenDBRS rcohenDBRS mentioned this issue Mar 21, 2019
Closed
@2opremio
Copy link
Contributor

@rcohenDBRS I think this should be fixed by #1851

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@squaremo squaremo

Labels
bug dogfood
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@squaremo @2opremio @rcohenDBRS