Hide Forgot
Log Tail: Pulled 2/2 layers, 100%!c(MISSING)omplete Extracting Pulling image golang:1.10.3 ... error: build error: no such image The % in the log tail is being interpreted as a format string. From api.ci.
Is that actually in the build object, or is that something oc describe is doing? I suspect the latter.
appears to be caused by lib/describe/helpers.go formatString(). Could happen to any field that has a valid format string.
Origin PR: https://github.com/openshift/origin/pull/21304
Origin PR has merged.
Verified in v4.0.0-0.80.0. oc set build-hook bc/ruby-ex --post-commit --script="echo '100%'; echo '100%'; for i in seq 20; do echo '100%'; done; /bin/notexist" oc start-build ruby-ex oc describe build # no error now Log Tail: 100% sh: /bin/notexist: No such file or directory subprocess exited with status 127 subprocess exited with status 127 error: build error: error building at step {Env:[PATH=/opt... 20; do echo '100%'; done; /bin/notexist'}: exit status 127
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