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

Bug 2094872

Summary:	oc logs unavailable
Product:	OpenShift Container Platform	Reporter:	Tom Dale <tdale>
Component:	oc	Assignee:	Maciej Szulik <maszulik>
oc sub component:	oc	QA Contact:	zhou ying <yinzhou>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	fleber, krmoser, mfojtik, tdale
Version:	4.11
Target Milestone:	---
Target Release:	---
Hardware:	s390x
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-10 11:47:00 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 Tom Dale 2022-06-08 14:05:35 UTC

Description of problem: On a fresh installed cluster on s390 (zVM or KVM) `oc logs pod/podname` and console gui logs tab are not showing any text for any pods. Pods from both openshift default projects and new applications have no logs.

Version-Release number of selected component (if applicable):
4.11.0-0.nightly-s390x-2022-06-07-102819

How reproducible:
Reinstalled 3 time with version 4.11.0-0.nightly-s390x-2022-06-07-102819

Steps to Reproduce:
1. oc login to cluster
2. oc get pods -A 
3. oc logs pod/<any pod found from #2> 

Actual results:
```
-> % oc logs pod/ovnkube-node-nl64v -n openshift-ovn-kubernetes -c ovnkube-node

-> % echo $?
0
```

Additional info:
Fresh cluster with no degraded operators or failing pods in any namespace. 
`oc debug pods ` is working fine.

Comment 1 Tom Dale 2022-06-08 15:39:18 UTC

Tested on today's build 4.11.0-0.nightly-s390x-2022-06-08-103008 and issue seems to be resolved.

Comment 2 Maciej Szulik 2022-06-10 11:47:00 UTC

Closing based on the previous comment.