Running the same build on 3.11 cluster and 4.3.0 cluster. Comparing the build time: #430 oc get build --context build01 -n ttt NAME TYPE FROM STATUS STARTED DURATION machine-os-content Docker Complete About an hour ago 1h22m0s #311 machine.os.content.debug oc get build NAME TYPE FROM STATUS STARTED DURATION machine-os-content Docker Complete About an hour ago 8m36s Reprod. steps: oc new-project ttt oc apply -f ttt.is.yaml oc apply -f machine-os-content.build.yaml The yamls and logs are attached. Related to https://bugzilla.redhat.com/show_bug.cgi?id=1784163
Created attachment 1659787 [details] imagestream
Created attachment 1659802 [details] build
Created attachment 1659825 [details] build log 430
Created attachment 1659846 [details] build log 311
Moving to the Containers team - root issues are with buildah. Needs to be moved back to Builds when ready to be vendored in.
Assigning to Nalin. I suspect this is related if not a duplicate to https://bugzilla.redhat.com/show_bug.cgi?id=1790525
(In reply to Tom Sweeney from comment #7) > Assigning to Nalin. I suspect this is related if not a duplicate to > https://bugzilla.redhat.com/show_bug.cgi?id=1790525 The big offenders in the 4.3 log compared to 3.11 happen during COPY instructions, and while one of them requires 4.3 to download an image, the majority of the time we spend on that instruction happens after the builder logs that the image was successfully pulled, so I do believe this is the same problem that we see in #1790525. The COPY implementation is getting an overhaul, but that work is still in progress, so I'm moving this to 4.5.
Taking a closer look at default-route-openshift-image-registry.apps.build01.ci.devcluster.openshift.com/test-image/pipeline@sha256:9ca3e5979408a90873226d80e4d2952715bd2a4cc9db647c9d8533c588409064, this should be fixed when #1790525's fix goes out. It doesn't require the rework I mentioned in comment 9, which targets cases where the source uses a .dockerignore file. Marking this as a duplicate instead. *** This bug has been marked as a duplicate of bug 1790525 ***