gloo
gloo copied to clipboard
[WIP] Update Statuses on Election Changes
Description
Please include a summary of the changes.
This bug fixes ... \ This new feature can be used to ...
Context
Users ran into this bug doing ... \ Users needed this feature to ...
Checklist:
- [ ] I included a concise, user-facing changelog (for details, see https://github.com/solo-io/go-utils/tree/master/changelogutils) which references the issue that is resolved.
- [ ] If I updated APIs (our protos) or helm values, I ran
make -B install-go-tools generated-codeto ensure there will be no code diff - [ ] I followed guidelines laid out in the Gloo Edge contribution guide
- [ ] I opened a draft PR or added the work in progress label if my PR is not ready for review
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests that prove my fix is effective or that my feature works
Visit the preview URL for this PR (updated for commit d0472d5):
https://gloo-edge--pr7151-ha-status-updates-zgki906v.web.app
(expires Mon, 10 Oct 2022 13:19:41 GMT)
🔥 via Firebase Hosting GitHub Action 🌎
Issues linked to changelog: https://github.com/solo-io/gloo/issues/7148
/kick
Step #10 - "test": WARN gloo.setup.gloosnapshot.event_loop.reporter failed to write status state:Accepted reported_by:"gloo" for resource local-test-upstream-35: error reading before applying status: default.local-test-upstream-35 does not exist
Step #10 - "test": DEBUG gloo.setup.gloosnapshot.event_loop Failed writing report for proxies: 1 error occurred:
Step #10 - "test": * failed to write status state:Accepted reported_by:"gloo" for resource local-test-upstream-35: error reading before applying status: default.local-test-upstream-35 does not exist
Step #10 - "test":
Step #10 - "test":
Step #10 - "test": DEBUG gloo.setup.gloosnapshot.event_loop proxy list updated {"len(proxyList)": 0, "currentHash": 14695981039346656037, "previousProxyStatusHash": 309446157695230754}
Step #10 - "test": ERROR gloo.setup gloo main event loop {"error": "event_loop.gloo: 1 error occurred:\n\t* writing reports: failed to write reports. did you make sure your CRDs have been updated since v1.13.0-beta14 of open-source? (i.e. `status` and `status.statuses` fields exist on your CR): 1 error occurred:\n\t* failed to write status state:Accepted reported_by:\"gloo\" for resource local-test-upstream-35: error reading before applying status: default.local-test-upstream-35 does not exist\n\n\n\n", "errorVerbose": "1 error occurred:\n\t* writing reports: failed to write reports. did you make sure your CRDs have been updated since v1.13.0-beta14 of open-source? (i.e. `status` and `status.statuses` fields exist on your CR): 1 error occurred:\n\t* failed to write status state:Accepted reported_by:\"gloo\" for resource local-test-upstream-35: error reading before applying status: default.local-test-upstream-35 does not exist\n\n\n\n\nevent_loop.gloo\ngithub.com/solo-io/go-utils/errutils.AggregateErrs\n\t/go/pkg/mod/github.com/solo-io/[email protected]/errutils/aggregate_errs.go:19\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1571"}
https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=9190545c-d96e-4515-88f5-cc3010257001
/kick build-bot passed but pushing empty commits doesn't cause a re-run
/kick build-bot passed but pushing empty commits doesn't cause a re-run