In https://issues.redhat.com/browse/OCPBUGS-14260, it was observed that if the source OCP payload was lower than 4.12.3 some issues were occurring during the seamless upgrade from WMCO 7.0.1 to 7.1.0 (due to a missing OVN path that merged in 4.12.3). As a consequence, a blocking statement was added in WMCO 7.1.0 to make sure the OCP payload installed was 4.12.3 or older. This works well and it doesn't imply any issues with stable releases. However, in our QE testing, nightly and ci releases are used, which all have the release identifer 4.12.0-0.nightly-<year>-<month>-<day>-<time> and 4.12.0-0.ci-<year>-<month>-<day>-<time>, as it can be observed in the releases page for [nightlies|https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/#4.12.0-0.nightly] and [ci|https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/#4.12.0-0.ci] builds.

This causes the following error when trying to install or upgrade any of these CI builds:

{"level":"error","ts":"2023-08-05T12:08:48Z","logger":"setup","msg":"failed to validate required cluster configuration","error":"invalid OCP version: current version is v4.12.0-0.nightly-2023-08-03-163056. minimum required version for WMCO 7.1.1-4a16077 is v4.12.3. please upgrade your cluster","stacktrace":"main.main\n\t/remote-source/build/windows-machine-config-operator/cmd/operator/main.go:106\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:250"}

Even thought this build is based on the most recent 4.12.28 release. 

The consequence is that we can't have any automatic regression testing on 4.12 for any cloud provider, as nightly builds are always used and there is not way to use "stable" builds in the format 4.12.28, 4.12.5, etc...

It would be very useful to improve this check so that WMCO doesn't block the installation when the build identifier includes the nightly or ci identifier.
 

4.12 and WMCO 7.1.0

Always

1.
2.
3.