Bug 1952457 - In k8s 1.21 bump '[sig-node] crictl should be able to run crictl on the node' test is disabled
Summary: In k8s 1.21 bump '[sig-node] crictl should be able to run crictl on the node'...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Sascha Grunert
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-22 10:11 UTC by Maciej Szulik
Modified: 2021-10-18 17:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:30:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26320 0 None None None 2021-08-30 14:57:21 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:30:35 UTC

Description Maciej Szulik 2021-04-22 10:11:50 UTC
In https://github.com/openshift/origin/pull/26054 I'm disabling

 [sig-node] crictl should be able to run crictl on the node 

test, which is consistently failing.

Comment 1 Maciej Szulik 2021-04-22 10:17:22 UTC
From looking at previous runs I can't find this tests being run before, so it might be that the e2eskipper is currently 
treating gcp where we run these tests as gce and includes this test. That's one of possible theories.

Comment 2 Ryan Phillips 2021-04-24 01:11:58 UTC
Peter, could you look into this?

Comment 3 Sascha Grunert 2021-04-28 08:16:25 UTC
Hey Maciej, may I ask you to share the test logs for a failing test? I was not able to find them on within the OpenShift prow instance.

Comment 4 Maciej Szulik 2021-04-28 13:00:09 UTC
(In reply to Sascha Grunert from comment #3)
> Hey Maciej, may I ask you to share the test logs for a failing test? I was
> not able to find them on within the OpenShift prow instance.

It's been a while, I'd probably suggest bringing the test back and get a fresh set of results.

Comment 5 Sascha Grunert 2021-04-29 08:01:03 UTC
As suggested in https://github.com/openshift/origin/pull/26054#discussion_r622163915, I'll wait for the PR to get merged to re-enable the test. Then we will see what's the actual issue is.

Comment 9 Sascha Grunert 2021-05-10 11:54:36 UTC
Re-enabling the test because I think it now gets automatically skipped: https://github.com/openshift/origin/pull/26144

Comment 10 Sascha Grunert 2021-05-10 12:33:14 UTC
Found the issue and I think making the upstream test more robust makes sense, opened https://github.com/kubernetes/kubernetes/pull/101866 for achieving this goal.

Comment 11 Sascha Grunert 2021-06-07 14:00:43 UTC
Unsetting the target release. The issue will be fixed upstream and automatically land in OpenShift.

Comment 12 Sascha Grunert 2021-07-12 09:32:37 UTC
Re-enabling the test in openshift/origin: https://github.com/openshift/origin/pull/26320

Comment 13 Sascha Grunert 2021-08-30 11:04:17 UTC
The test get's now automatically skipped and is just requiring review.

Ref https://github.com/openshift/origin/pull/26320

Comment 19 errata-xmlrpc 2021-10-18 17:30: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


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