[Flaking] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate

[pacoxu]

Failure cluster 2dc5e72feecececa1727

https://storage.googleapis.com/k8s-triage/index.html?test=should%20surge%20pods%20onto%20nodes%20when%20spec%20was%20updated%20and%20update%20strategy%20is%20RollingUpdate

Error text:

[FAILED] invariants were violated during daemonset update:
An old pod with UID bddc4da1-7cb5-404f-825f-ff62ecb12ec4 has been running alongside a newer version for longer than 1m0s
In [It] at: test/e2e/apps/daemon_set.go:813 @ 10/30/23 14:43:33.844

Recent failures:

2023/11/8 23:32:39 ci-kubernetes-e2e-gci-gce-serial
2023/11/8 16:56:39 ci-kubernetes-e2e-gce-cos-k8sstable1-serial
2023/11/8 05:23:06 ci-kubernetes-soak-gci-gce-stable2
2023/11/5 10:15:26 ci-kubernetes-e2e-gci-gce-serial
2023/11/4 12:58:25 ci-kubernetes-e2e-gci-gce-serial

/kind flake
/sig apps

This is an old flaking since #107174, but the flaky rate is not that high.

The rate in recent runs in https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial is about 3/23 ~ 13%.

[pacoxu]

/priority backlog
as the failure rate now is not high
/cc @soltysh

• old threads in [Flaky Test] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate [Feature:DaemonSetUpdateSurge] #100138 and [Flaky Test][sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate #107174

[k8s-ci-robot]

@pacoxu: The label(s) priority/backlog\ cannot be applied, because the repository doesn't have them.

In response to this:

/priority backlog
as the failure rate now is not high
/cc @soltysh

• old threads in [Flaky Test] [sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate [Feature:DaemonSetUpdateSurge] #100138 and [Flaky Test][sig-apps] Daemon set [Serial] should surge pods onto nodes when spec was updated and update strategy is RollingUpdate #107174

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.

[pacoxu]

/priority backlog

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[pacoxu]

/remove-lifecycle rotten
still flaking

[atiratree]

/triage accepted
/assign