-
Notifications
You must be signed in to change notification settings - Fork 64
Updates to the controller logic to better handle failures in etc updates #424
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
Conversation
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.
Thanks for the PR, please address the review
Something is off with this PR, I built an image from your branch and submitted just 1 AW, it does not run, log message:
image used: |
Updated test messages. Minor cleanups in the e2e tests.
Fixed warning in go.mod file
Fixed failed test Log message improvements
I restarted the build, it was still failing with some updateEtcd failures. |
e2e test updates.
Fixed Failing test
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.
All test cases pass on the laptop, Scheduling fail fast test case is now passing post changes.
All except 1 test pass. the 1 test is pending by design, it is a bad AW and the system rejects, below is the test:
The test should be changed, it should pass when such AW is never dispatched. We need to figure stop failing builds for tests that are pending until the test is changed. |
Updated the ETCD update functions.
Added error handling.
Reduce the calls to update.