Description of problem: When view logs of a particular build by version, will meet error: cannot specify a version and a build Version-Release number of selected component (if applicable): oc v3.11.0-0.10.0 kubernetes v1.11.0+d4cacc0 openshift v3.11.0-0.10.0 How reproducible: always Steps to Reproduce: 1. Create a BC and trigger build; 2. View logs of a particular build by version `oc logs bc/ruby-sample-build --version=1` Actual results: 2. Met error: cannot specify a version and a build Expected results: 2. Should view the logs of a particular build by version Additional info:
Origin PR: https://github.com/openshift/origin/pull/20536
Confirmed with latest ocp, the issue has fixed: oc v3.11.0-0.13.0 openshift v3.11.0-0.13.0 kubernetes v1.11.0+d4cacc0 [root@192 ~]# oc logs bc/ruby-ex --version=2 Cloning "https://github.com/sclorg/ruby-ex.git" ... Commit: bbb670185b6ce67294cc461ae9c18710e6f26089 (Merge pull request #18 from durandom/master) Author: Ben Parees <bparees.github.com> Date: Thu Dec 7 14:53:36 2017 -0500 Using centos/ruby-25-centos7@sha256:948ca9ba15936a8fbe25dd2b5af7526747863ee85adae8178ae56e0892ca9965 as the s2i builder image ---> Installing application source ... ---> Building your Ruby application from source ... ---> Running 'bundle install --retry 2 --deployment --without development:test' ... Fetching gem metadata from https://rubygems.org/.............. Using bundler 1.16.1 Fetching puma 3.10.0 Installing puma 3.10.0 with native extensions Fetching rack 2.0.3 Installing rack 2.0.3 Bundle complete! 2 Gemfile dependencies, 3 gems now installed. Gems in the groups development and test were not installed. Bundled gems are installed into `./bundle` ---> Cleaning up unused ruby gems ... Running `bundle clean --verbose` with bundler 1.16.1 Frozen, using resolution from the lockfile Pushing image docker-registry.default.svc:5000/zhouy/ruby-ex:latest ... Pushed 5/10 layers, 50% complete Pushed 6/10 layers, 60% complete Pushed 7/10 layers, 70% complete Pushed 8/10 layers, 80% complete Pushed 9/10 layers, 90% complete Pushed 10/10 layers, 100% complete Push successful
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:0407