Bug 2000589

Summary:	[sig-node] crictl should be able to run crictl on the node
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	Node	Assignee:	Sascha Grunert <sgrunert>
Node sub component:	CRI-O	QA Contact:	Sunil Choudhary <schoudha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, nagrawal, sippy, tremes
Version:	4.9
Target Milestone:	---
Target Release:	4.9.0
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:	2021-10-18 17:51:04 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 Stephen Benjamin 2021-09-02 12:57:52 UTC

[sig-node] crictl should be able to run crictl on the node [Suite:openshift/conformance/parallel] [Suite:k8s]

This test was enabled in https://github.com/openshift/origin/pull/26320, but it's basically permafailing ever since.

See https://github.com/openshift/origin/pull/26320#issuecomment-911626099 for more info.


Error message:
 	
fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Sep  2 10:36:51.645: Ran "sudo crictl version" on "10.0.0.5:22", got error error getting SSH client to core@:22: dial tcp :22: connect: connection refused


Looking at the test code I can't figure out why the IP is available in crictl.go ("Ran x on 10.0.0.5:22") but the IP is missing in the SSH method.

Comment 2 Sascha Grunert 2021-09-02 13:59:37 UTC

Revert in https://github.com/openshift/origin/pull/26444, the test should be green in 4.10 where we made the crictl test host-local (https://github.com/kubernetes/kubernetes/pull/103640).

Comment 5 Sunil Choudhary 2021-09-05 17:42:21 UTC

Test is reverted in https://github.com/openshift/origin/pull/26444

Comment 8 errata-xmlrpc 2021-10-18 17:51:04 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759