-
Bug
-
Resolution: Can't Do
-
Undefined
-
None
-
4.14.z, 4.15.z
-
None
-
Moderate
-
False
-
Description of problem:
Application builds can fail on an error 500 when using the Internal Registry configured with Noobaa as the backend.
Version-Release number of selected component (if applicable):
I have seen this issue in two clusters running 4.14.z and one cluster running 4.15.z
How reproducible:
Install a new cluster, configure ODF, change the internal registry to use Noobaa-backed S3 storage, then attempt an application build
Steps to Reproduce:
1. Install a cluster
2. Install/Configure ODF
3. Configure the internal OCP registry to use a Noobaa bucket as back-end storage via S3
4. Run an S2I build
5. The noobaa-default-backing-store-noobaa-pod-XXXXXX pod in the openshift-storage namespace will get OOMKilled during the push to the registry
Actual results:
The build fails to push the image to the internal registry and the Default BackingStore will go into "Phase: Rejected" until the backingstore pod restarts.
Expected results:
The build should succeed.
Additional info:
KCS 7062227 has been created and contains more information.
