Bug 1952929

Description of problem:

Note that customer is on Azure platform.

Customer is using 'oc start-build' as part of a pipeline. They have noticed (with about a 1 in 10 occurrence?) that when they use '--from-file' this process sometimes corrupts exactly one byte of a jar file being copied into the container image to the '/deployments' directory. When they use '--from-dir' instead, the corruption does not seem to happen.


Version-Release number of selected component (if applicable):

OCP4.6.x + Azure platform (customer says that this did not happen on 4.5.x + AWS platform and that their build process has not been changed)


Steps to Reproduce:

# 1. Verify jar on jenkins agent pod
14:06:24  + jar xf target.jar
# 2. Print size of the jar on jenkins agent pod
14:06:25  + ls -al target.jar
14:06:25  -rw-r--r--. 1 1001 root 91351065 Apr 16 12:06 target.jar

[at this point, the jar file is the correct size]

# 3. Copy jar to persistent pod in order to analyze
14:06:26  + oc rsh example-0 bash -c 'mkdir -p /usr/share/nginx/html/test'
14:06:34  + oc cp target.jar example-0:/usr/share/nginx/html/test/
# 4. Print size of the jar on persistent pod 
14:06:36  + oc rsh example-0 bash -c 'ls -al target.jar'
14:06:36  -rw-r--r--. 1 1001 root 91351065 Apr 16 12:06 target.jar

[at this point, the jar file is still the correct size]

# 5. Run oc start-build, that build the image with input jar and push it to the repository
14:06:37  + oc start-build bc/target-service --from-file=target.jar

[after this point, the jar file is not the correct size (-1 byte) when the /deployments directory is examined and also "Error: Invalid or corrupt jarfile" is produced in the log]

If the customer uses '--from-dir' instead of --from-file' in the oc start-build command, the corruption does not seem to happen.


Actual results:
target.jar is exactly one byte short after being copied to the /deployments directory (happens about 10% of the time) when using --from-file.


Expected results:
target.jar is copied intact every time.

Additional info:
Please see the attachments for more process details and logs.