-
Bug
-
Resolution: Done
-
Major
-
4.13.z, 4.11.z, 4.14.z
-
Moderate
-
No
-
False
-
a few e2e tests are failing due to x86 image pull by default
1. [sig-builds][Feature:Builds] oc new-app should succeed with a --name of 58 characters [apigroup:build.openshift.io] [Skipped:Disconnected] [Skipped:Proxy] [Suite:openshift/conformance/parallel] 2. [sig-builds][Feature:Builds] build can reference a cluster service with a build being created from new-build should be able to run a build that references a cluster service [apigroup:build.openshift.io] [Skipped:Disconnected] [Skipped:Proxy] [Suite:openshift/conformance/parallel]
Note: Test case 1 can be verified manually by creating an app with name less than, equal to and greater than 58 characters.
must-gather log file
output.log file
Version-Release number of selected component (if applicable):
4.11.z, 4.13.z, 4.14.z
How reproducible:
This e2e failure is consistently reproduceable.
Steps to Reproduce:
1.Start a Z stream testing 2.monitor e2e
Actual results:
e2e is getting failed
Expected results:
e2e should pass
Additional info: