-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Extended.[k8s.io] Daemon set [Serial] Should adopt or recreate existing pods when creating a RollingUpdate DaemonSet with matching or mismatching templateGeneration #14129
Comments
(and i have no idea why it failed when it expected "0" to be "0") |
upstream flake: claimed fix: the referenced fix is in origin, so it must be upset for another reason. |
@marun -- can you help track this down further? |
I think this is also in part kubernetes/kubernetes#50586 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1312/testReport/junit/(root)/Extended/_k8s_io__Daemon_set__Serial__Should_adopt_or_recreate_existing_pods_when_creating_a_RollingUpdate_DaemonSet_with_matching_or_mismatching_templateGeneration/
The text was updated successfully, but these errors were encountered: