[Flaking Test] ci-kubernetes-unit (error message's order sensitivity) about kubernetes HOT 5 CLOSED

/remove-sig testing
/sig scheduling
(sig testing doesn't own all of the unit tests, just test frameworks, tooling, CI infra, etc)

This appears to be a flake in scheduler unit tests which would be sig scheduling (

from kubernetes.

.. and it appears to be DRA specific subset of scheduling so
/sig node
as well

from kubernetes.

FYI - looks like this is happening every 3-6 hours give or take. Yesterday it was every six hours and today it seems to be every 3-4 hours.

Looking into it a bit more, it looks like it may just be an issue with a connection via the test while it's trying to hit the server. I don't think the test itself is failing, I think the connection to the server is failing.

CC @Vyom-Yadav

from kubernetes.

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from kubernetes.

Hey All - hope you're well. Michael here from the Release Signal team.

Just wanted to touch base and make sure we're good to go for the cut on the 4th.

CC @BenTheElder
/sig-node

from kubernetes.