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

Bug 1857597

Summary:	Some of `oc adm inspect co/xx` failed with error
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	alegrand, anpicker, aos-bugs, erooth, jmalde, jokerman, kakkoyun, lcosic, mfojtik, mloibl, pkrupa, rgregory, surbania, yinzhou
Target Milestone:	---
Target Release:	4.4.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-28 12:37:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1817938
Bug Blocks:

Comment 4 Junqi Zhao 2020-07-20 03:36:28 UTC

Tested with 4.4.0-0.nightly-2020-07-18-033102
# oc adm inspect co/monitoring
Gathering data for ns/openshift-monitoring...
E0719 23:13:52.725595   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod c2b8eda6d05afdd930669f9c6f57670f42ff57ad243a3bd87d7607fa990e75d2, uid : exit status 1: 2020/07/20 03:19:00 socat[187426] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:52.859161   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod c2b8eda6d05afdd930669f9c6f57670f42ff57ad243a3bd87d7607fa990e75d2, uid : exit status 1: 2020/07/20 03:19:01 socat[187433] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:53.002687   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod c2b8eda6d05afdd930669f9c6f57670f42ff57ad243a3bd87d7607fa990e75d2, uid : exit status 1: 2020/07/20 03:19:01 socat[187439] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:53.143916   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod c2b8eda6d05afdd930669f9c6f57670f42ff57ad243a3bd87d7607fa990e75d2, uid : exit status 1: 2020/07/20 03:19:01 socat[187446] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:54.291718   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod 48dcd9eef02f7b7614dbfe6d6e4a98cfbca89f72971ab9b2d9b8c9c729e64f32, uid : exit status 1: 2020/07/20 03:19:02 socat[325305] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:54.434303   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod 48dcd9eef02f7b7614dbfe6d6e4a98cfbca89f72971ab9b2d9b8c9c729e64f32, uid : exit status 1: 2020/07/20 03:19:02 socat[325340] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:54.576302   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod 48dcd9eef02f7b7614dbfe6d6e4a98cfbca89f72971ab9b2d9b8c9c729e64f32, uid : exit status 1: 2020/07/20 03:19:02 socat[325346] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:54.713329   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod 48dcd9eef02f7b7614dbfe6d6e4a98cfbca89f72971ab9b2d9b8c9c729e64f32, uid : exit status 1: 2020/07/20 03:19:02 socat[325353] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:55.889376   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod e19cddc351f3d4af6b63f2b7be23eb92dff41ad056920c73993c813c57aceecd, uid : exit status 1: 2020/07/20 03:19:04 socat[189453] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:56.043427   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod e19cddc351f3d4af6b63f2b7be23eb92dff41ad056920c73993c813c57aceecd, uid : exit status 1: 2020/07/20 03:19:04 socat[189461] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:56.212455   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod e19cddc351f3d4af6b63f2b7be23eb92dff41ad056920c73993c813c57aceecd, uid : exit status 1: 2020/07/20 03:19:04 socat[189484] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:13:56.351187   18795 portforward.go:400] an error occurred forwarding 37587 -> 9094: error forwarding port 9094 to pod e19cddc351f3d4af6b63f2b7be23eb92dff41ad056920c73993c813c57aceecd, uid : exit status 1: 2020/07/20 03:19:04 socat[189499] E connect(5, AF=2 127.0.0.1:9094, 16): Connection refused
E0719 23:14:41.300567   18795 portforward.go:385] error copying from local connection to remote stream: tls: use of closed connection
Wrote inspect data to inspect.local.5281839411889778455.

Although there is portforward error, it does not affect the function, move to VERIFIED, feel free to reopen it if you think it is a bug

Comment 6 errata-xmlrpc 2020-07-28 12:37:03 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-2020:3075