Blocking errors if oc binary in OCP 4 is not found in mirrors #495
Comments
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 22, 2022
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 22, 2022
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 22, 2022
4 tasks
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 23, 2022
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 24, 2022
mcarlett
added a commit
to mcarlett/xtf
that referenced
this issue
Jun 24, 2022
mnovak1
pushed a commit
that referenced
this issue
Jun 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using latest version of OCP4 (4.10.19) the XTF library will generate runtime errors because the version is not yet released in the public mirror https://mirror.openshift.com/pub/openshift-v4/clients/ocp/
In general if the version is not in the mirror the XTF library will fail and no fallback action are implemented
java.lang.IllegalStateException: Failed to download and extract oc binary from https://mirror.openshift.com/pub/openshift-v4/amd64/clients/ocp/4.10.19/openshift-client-linux.tar.gz at cz.xtf.core.openshift.ClusterVersionOpenShiftBinaryPathResolver.getCachedOrDownloadClientArchive(ClusterVersionOpenShiftBinaryPathResolver.java:144)The text was updated successfully, but these errors were encountered: