Bug 1521026 – [3.6] oc logs fails with unexpected stream type ""

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1521026 - [3.6] oc logs fails with unexpected stream type "" [NEEDINFO]

Summary:	[3.6] oc logs fails with unexpected stream type ""

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	3.6.z
Assigned To:	Seth Jennings
QA Contact:	DeShuai Ma
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1503458
Blocks:
	Show dependency tree / graph

Reported:	2017-12-05 11:14 EST by Seth Jennings
Modified:	2018-01-23 12:59 EST (History)
CC List:	12 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Fixes issue where "oc logs" exits with error "unexpected stream type".
Story Points:	---
Clone Of:	1503458
Environment:
Last Closed:	2018-01-23 12:59:00 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	bmchugh: needinfo? (dma)

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0113	normal	SHIPPED_LIVE	OpenShift Container Platform 3.7 and 3.6 bug fix and enhancement update	2018-01-23 17:55:59 EST

Groups: None (edit)

Comment 3 Xiaoli Tian 2017-12-12 22:06:26 EST

Move it to ON_QA to test as the fix has been built in latest 3.6.z build at least.

Comment 4 DeShuai Ma 2017-12-13 02:25:17 EST

Verify on v3.6.173.0.83
oc logs can get pod logs successfully and no error.

Comment 8 errata-xmlrpc 2018-01-23 12:59:00 EST

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-2018:0113

Note You need to log in before you can comment on or make changes to this bug.