Flaky Test: Topology Aware Scheduling when Negative scenarios for ClusterQueue configuration should mark TAS ClusterQueue as inactive if used in cohort

[tenzen-y]

What happened:

Failure on "TopologyAwareScheduling Suite: [It] Topology Aware Scheduling when Negative scenarios for ClusterQueue configuration should mark TAS ClusterQueue as inactive if used in cohort"

{Timed out after 5.000s.
Expected object to be comparable, diff:   []v1.Condition{
  	{
  		... // 2 ignored and 2 identical fields
  		Reason: "NotSupportedWithTopologyAwareScheduling",
  		Message: strings.Join({
  			"Can't admit new workloads: TAS is not supported for cohorts",
- 			`, there is no Topology "default" for TAS flavor "tas-flavor"`,
  			".",
  		}, ""),
  	},
  }
 failed [FAILED] Timed out after 5.000s.
Expected object to be comparable, diff:   []v1.Condition{
  	{
  		... // 2 ignored and 2 identical fields
  		Reason: "NotSupportedWithTopologyAwareScheduling",
  		Message: strings.Join({
  			"Can't admit new workloads: TAS is not supported for cohorts",
- 			`, there is no Topology "default" for TAS flavor "tas-flavor"`,
  			".",
  		}, ""),
  	},
  }
In [It] at: /home/prow/go/src/kubernetes-sigs/kueue/test/integration/tas/tas_test.go:112 @ 01/22/25 04:30:36.473
}

What you expected to happen:

Succeeded

How to reproduce it (as minimally and precisely as possible):

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-kueue-test-integration-release-0-9/1881918244332244992

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Kueue version (use git describe --tags --dirty --always):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[tenzen-y]

/kind flake

[mimowo]

/assign
Let me check, it seems like a race condition with processing the topology ADDED event and creating the message.

I think we can just relax the assert and only check the reason "NotSupportedWithTopologyAwareScheduling". The message is tested at the unit tests level.