Description of problem:
When following the steps:
Tutorial: Building local code changes
it fails when a filename contains an umlaut
[quicklab@master-0 ruby-hello-world]$ oc start-build ruby-hello-world --from-dir="." --follow
Uploading directory "." as binary input for the build ...
build "ruby-hello-world-13" started
Receiving source from STDIN as archive ...
error: unable to extract binary build input, must be a zip, tar, or gzipped tar, or specified as a file: exit status 1
no further useful info can be found in the logs
Version-Release number of selected component (if applicable):
tested with 3.10 (as customer)
Follow all the steps in:
but in step 4 just rename the ruby file to contain an umlaut:
[quicklab@master-0 test]$ pwd
error described is thrown and build is failing
build working or a meaningful error is thrown
customer states you cannot always prevent that a umlaut gets used and it took very long to find the issue so it should be fixed
I wonder if this is also a problem for git repos that contain a file w/ an umlaut, or it's specific to how the binary build tars+streams the content in. We should check.
Origin PR: https://github.com/openshift/origin/pull/22388
Builder PR: https://github.com/openshift/builder/pull/55
origin PR has merged. Builder PR adds additional debugging info.
payload: image: registry.svc.ci.openshift.org/ocp/release@sha256:2d781cbe28722b6eeb3ff969c5dc68199198fd1f0514a3284eb7215ae0cb4d2f
1. Create files with include umlaut, like utf8_tést_app.rb
2. Start build from with local source, build complete
[wewang@Desktop ruby]$ ls
config.ru Dockerfile Gemfile utf8_tést_app.rb
$ oc start-build ruby-hello-world --from-dir="." --follow
$ oc get builds
NAME TYPE FROM STATUS STARTED DURATION
ruby-hello-world-1 Docker Git@787f1be Complete 12 minutes ago 1m23s
ruby-hello-world-2 Docker Binary Complete 6 minutes ago 1m7s
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.