-
Bug
-
Resolution: Unresolved
-
Normal
-
4.20.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
+
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The Regex Check: The [sig-scheduling][Early] control plane machine set operator should not cause an early rollout test runs the regex.MatchString() function with this machine name.
Pattern: ^([a-zA-Z0-9])+master\d$
String: mq6cnk8l-e3290-468r7-master-hbggj-2
The Result: The regex engine determines that the string master-hbggj-2 does not match the pattern master-\d+ because hbggj is not a sequence of digits. The MatchString function returns false.
Failing tests:
[sig-cluster-lifecycle][Feature:Machines] Managed cluster should [sig-scheduling][Early] control plane machine set operator should not cause an early rollout [Suite:openshift/conformance/parallel]
STEP: Creating a kubernetes client @ 08/12/25 16:22:37.162
STEP: checking for the openshift machine api operator @ 08/12/25 16:22:37.164
STEP: ensuring every node is linked to a machine api resource @ 08/12/25 16:22:37.22
[FAILED] in [It] - github.com/openshift/origin/test/extended/machines/machines.go:143 @ 08/12/25 16:22:37.239
fail [github.com/openshift/origin/test/extended/machines/machines.go:143]: unexpected name of a control machine occured during early stages: mq6cnk8l-e3290-468r7-master-hbggj-2
Expected
<bool>: false
to be true
The issue is that master-\d+, looks for one or more digits after master-. The failing example master-hbggj-2 has a mix of letters, a hyphen, and digits.
A new pattern could be:
pattern := `^([a-zA-Z0-9]+-)+master(?:-[a-zA-Z0-9]+)?-\d+$`
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
fail [github.com/openshift/origin/test/extended/machines/machines.go:143]: unexpected name of a control machine occured during early stages: 6l5kgcdr-1ec94-4tnlh-master-gkjmq-0 Expected <bool>: false to be true
Expected results:
Match
Additional info: