Hide Forgot
Created attachment 1559182 [details] error occurrences Description of problem: Version-Release number of selected component (if applicable): 4.1 How reproducible: consistently happening on CI for aws jobs https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/267/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-upgrade/24 https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/267/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws-operator/1428 https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/267/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws/1339 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is this a matter of waiting longer for imagestream import controller?
We believe this could be due to the POST on ImageStreams taking more than the thirty second client timeout, due to the fact that we reference ~130 ImageStreamTags in that process and need to do the SAR checks for each one serially even if they are identical. I've written a patch to help with this [1] [1] https://github.com/openshift/origin/pull/22689
Passed in the test of 4.1.0-0.nightly-2019-05-08-131137: https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-serial-4.1/172#openshift-tests-monitor-cluster-while-tests-execute
Sorry, verify the wrong CI test, change back to ON_QA for further verify.
QE have tried to created an ImageStream is created with a large number of tags that reference other ImageStreamTags in the same namespace and also check recent ci test, all passed, so mark this bug to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758