-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add detailed work request errors when work-request is failed for both Loadbalancer and Machines #378
Conversation
This is the output of make test: Unit tests are passing.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good. Thanks for doing that. I'll work on running the E2E tests.
e2e tests
|
This is manual testing in my local, simulated a case where instance launch fails(i.e. createInstance work-request failed and is stuck at 5%). The original reason and the reason shown in events match with the work-request-error of the create-wr failure. This fix seems to be working:
The bold part is the new introduction. |
…r both Loadbalancer and Machines (#378)
What this PR does / why we need it:
It provides more detailed insight as to why the work-request failed in the creation/updation of LB and compute resourceds. This is to ensure there is better readibility and understanding from the logs. A new workRequestClient is introduced to fetch the work-request errors for a specific work-request id and retrieve the messages associated with this work-request and record them as events/reconcile errors in logs.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #360