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
Bug 1904133: kubeletcfg: fix repeated status error msg #2369
Conversation
@QiWang19: This pull request references Bugzilla bug 1904133, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@QiWang19: This pull request references Bugzilla bug 1904133, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @cgwalters |
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.
Just reading this you'll end up with the same err msg with updated timestamp so itll just stay 1 message? Makes sense
But can you update your commit message to indicate this is a kubelet config change?
kubelet config does not append new status conditions if error message stays the same to avoid the repeated same conditions This patch mirrors the handlerErr of the container runtime config controller. Signed-off-by: Qi Wang <qiwan@redhat.com>
@QiWang19: This pull request references Bugzilla bug 1904133, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kikisdeliveryservice PTAL. I changed the commit message to note it's a kubelet config change. |
/retest |
1 similar comment
/retest |
/test e2e-agnostic-upgrade |
/test e2e-aws-workers-rhel7 |
/test e2e-aws-workers-rhel7 |
the rhel7 job is red no worries on retesting. /skip |
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 changes @QiWang19
for final approval:
/assign @rphillips
/skip |
/assign @rphillips |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kikisdeliveryservice, QiWang19, rphillips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
10 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@QiWang19: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@QiWang19: All pull requests linked via external trackers have merged: Bugzilla bug 1904133 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1904133
Signed-off-by: Qi Wang qiwan@redhat.com
- What I did
For kubeletconfig, do not append new status conditions if the error message stays the same
to avoid the repeated same conditions
This patch mirrors the handlerErr of the container runtime config controller.
- How to verify it
Verify this by applying the problematic YAML and waiting for several minutes to check the status
- Description for the changelog