Bug 2094919 - etcd vertical scaling test destabilizes vsphere
Summary: etcd vertical scaling test destabilizes vsphere
Keywords:
Status: CLOSED DUPLICATE of bug 2095703
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dean West
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-08 15:47 UTC by Stephen Benjamin
Modified: 2022-06-16 14:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 14:19:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27236 0 None open Bug 2094919: Skip etcd vertical scaling test on vsphere 2022-06-08 19:28:09 UTC

Description Stephen Benjamin 2022-06-08 15:47:51 UTC 
vpshere serial is permafailing on `[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state`, with TargetDown alerts for various components.

- This started around 5/11, which is when https://github.com/openshift/origin/pull/26917 ended up in the first payload

- TargetDown alerts always happens directly after the etcd vertical scale test. 



Example run: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-vsphere-serial/1532975513713250304

If you look at the intervals chart filtered by "TargetDown|vertical" you can see the behavior.  This happens on every vsphere serial job.
Comment 1 Stephen Benjamin 2022-06-08 19:27:15 UTC 
https://github.com/openshift/origin/pull/27236 disables the test on vsphere, and it passed vsphere-serial.  This does seem to be the problem.
Comment 3 Stephen Benjamin 2022-06-09 10:42:58 UTC 
Setting back to new, the merged PR was just disabling it temporarily.
Note You need to log in before you can comment on or make changes to this bug.