-
Notifications
You must be signed in to change notification settings - Fork 140
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
Continue waiting when an exception is raised #408
Continue waiting when an exception is raised #408
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.
Could you add a changelog fragment? Otherwise, LGTM
done |
I am testing your PR on my side, but unfortunately the Error was not eliminated. This is the result on my testing environment (sorry not RHEL, but macOS). I tested by just rebooting the target OCP4 node.
I suppose this block caused the above error. kubernetes.core/plugins/module_utils/common.py Lines 424 to 435 in df9968e
|
Indeed this piece of code was also part of the fix but forgot to commit it.
@sugitk thanks for the feedback |
@abikouo Thank you very much for your quick review, I will try your branch tomorrow. (now it's 11pm here..) |
@abikouo Good morning. I have tested with your branch (ex_wait), it worked as expected! |
Thanks for the feedback!! |
recheck |
@gravesm Do you have time to review this PR to merge? The customer is waiting for the fix.. |
@Akasurde could you please add your review here ? Thanks |
recheck |
Continue waiting when an exception is raised SUMMARY When an exception is raised and the wait_timeout is not reached, we should continue waiting as this may occurs due to temporary issue on cluster Fixes ansible-collections#407 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mike Graves <mgraves@redhat.com> Reviewed-by: Abhijeet Kasurde <None> (cherry picked from commit f418353)
Continue waiting when an exception is raised SUMMARY When an exception is raised and the wait_timeout is not reached, we should continue waiting as this may occurs due to temporary issue on cluster Fixes ansible-collections#407 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mike Graves <mgraves@redhat.com> Reviewed-by: Abhijeet Kasurde <None> (cherry picked from commit f418353)
) [backport/2.3] continue waiting when an exception is raised (#408) Depends-On: #446 Continue waiting when an exception is raised SUMMARY When an exception is raised and the wait_timeout is not reached, we should continue waiting as this may occurs due to temporary issue on cluster Fixes #407 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mike Graves mgraves@redhat.com Reviewed-by: Abhijeet Kasurde (cherry picked from commit f418353)
Previous to ansible-collections/kubernetes.core#408 an attempt to list resources for which the user was not authorized resulted in an unhandled exception. The task now does not fail, but instead reports the error message.
* Fix integration tests for k8s 2.3 Previous to ansible-collections/kubernetes.core#408 an attempt to list resources for which the user was not authorized resulted in an unhandled exception. The task now does not fail, but instead reports the error message. * try to fix sanity * Fix tests * fix tests * fix tests * Revert change to downstream build
Port changes from commit f418353 to the refactored code.
SUMMARY
When an exception is raised and the wait_timeout is not reached, we should continue waiting as this may occurs due to temporary issue on cluster
Fixes #407
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION