Bug 2038389 - Failing test: [sig-arch] events should not repeat pathologically
Summary: Failing test: [sig-arch] events should not repeat pathologically
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Hemant Kumar
QA Contact: Penghao Wang
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-07 19:12 UTC by Mike Dame
Modified: 2023-09-15 01:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-storage-operator pull 252 0 None Merged Bug 2038389: Union upgradeable conditions as well from ClusterCSIDriver objects 2022-01-14 15:32:49 UTC
Github openshift origin pull 26737 0 None open Bug 2038389: Fix vsphere testing workarounds 2022-01-14 15:32:50 UTC
Github openshift vmware-vsphere-csi-driver-operator pull 65 0 None Merged Bug 2038389: Avoid event spam for same events 2022-01-14 15:32:51 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:54 UTC

Description Mike Dame 2022-01-07 19:12:37 UTC
Working on the 1.23 rebase (https://github.com/openshift/kubernetes/pull/1087) we are seeing failures in the above test that look like:

1 events happened too frequently

event happened 314 times, something is wrong: ns/openshift-cluster-csi-drivers deployment/vmware-vsphere-csi-driver-operator - reason/check_deprecated_hw_version Marking cluster un-upgradeable because node control-plane-1 has hardware version vmx-13, which is below the minimum required version 15

See https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/1087/pull-ci-openshift-kubernetes-master-e2e-vsphere/1479262132649332736

Comment 1 David Eads 2022-01-07 19:19:55 UTC
314 event emissions is excessive.  Also, the cluster is not upgradeable=false.  `csi.vsphere.vmware.com` lists it in status, but no clusteroperator is reflecting it.

Comment 2 Tomas Smetana 2022-01-10 08:15:47 UTC
Reassigning: this is not an oVirt problem.

Comment 3 Tomas Smetana 2022-01-10 09:54:00 UTC
Bumping sev/prio: this is currently blocking k8s upgrade in 4.10.

Comment 4 Joseph Callen 2022-01-10 21:50:08 UTC
The UPI jobs randomly select a hardware version. That way we can test the various supported versions per release of OCP. 
the openshift/kubernetes vsphere job config should be running on IPI not UPI. Using IPI will select the correct hardware version for the vsphere infrastructure.


Comment 13 errata-xmlrpc 2022-03-10 16:37:38 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.10.3 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.


Comment 14 Red Hat Bugzilla 2023-09-15 01:18:36 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days

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