Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sorry for empty description. New bugzilla saved the bz before I could fill it out. Description of problem: In 4.0, the second and subsequent builds of an s2i application are pushing all layers, not just the changed top layer. This is resulting in much longer incremental builds times than previous releases. Example, django-psql-example normally builds in ~3 minutes for the initial build and then ~20 seconds thereafter when re-built in the same project. In 4.0, each build in a project takes ~3 minutes, whether initial or subsequent. Starting this bz with Image Registry, but maybe it is s2i? Version-Release number of selected component (if applicable): 4.0 as installed by next-gen installer on 12/10 How reproducible: Always Steps to Reproduce: 1. oc new-project test 2. oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git 3. oc get builds ruby-ex-1 Source Git@887f01c Complete 2 minutes ago 2m43s 4. oc start-build ruby-ex 5. oc get builds Actual results: ruby-ex-1 Source Git@887f01c Complete 7 minutes ago 2m43s ruby-ex-2 Source Git@887f01c Complete 3 minutes ago 2m30s Build log (attached) shows all layers pushed for the second build. Expected results: The second build should be much faster and only the modified application layer is pushed. Additional info: Build and registry logs attached
Created attachment 1513220 [details] build logs, registry log, imageregistry crd
This is an issue w/ buildah's management of image layers and how it pushes layers, transferring to that team. I know they are working on some aspects of this already, but i'm glad to hear the performance team is monitoring the issue as well.
Ben isn't this fixed now with the latest buildah?
Dan, I think it is, but Nalin would know for sure or how close it is if not.
Fixed in the current release.
https://bugzilla.redhat.com/show_bug.cgi?id=1682978 is blocking this issue to move to verified
Verified on 4.0.0-0.nightly-2019-03-06-074438 Registry pushes are now faster in 4.0 than in 3.11
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