Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1612021

Summary:	Can't view the logs of a particular build by version
Product:	OpenShift Container Platform	Reporter:	zhou ying <yinzhou>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Build version was not allowed to be specified when requesting logs. Consequence: Users were not able to view logs of specific build revisions. Fix: Allow specifying revision number by removing validation. Result: oc logs can be invoked for a specific build version.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-14 02:17:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description zhou ying 2018-08-03 09:28:41 UTC

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:

Comment 1 Juan Vallejo 2018-08-03 20:00:08 UTC

Origin PR: https://github.com/openshift/origin/pull/20536

Comment 2 zhou ying 2018-08-13 07:44:20 UTC

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

Comment 5 errata-xmlrpc 2019-03-14 02:17:59 UTC

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