Bug 1929748

Summary:	Upgrade from 4.7.0-rc2 to 4.8.0 fails [sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early]
Product:	OpenShift Container Platform	Reporter:	Federico Paolinelli <fpaoline>
Component:	Monitoring	Assignee:	Lili Cosic <lcosic>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.8	CC:	alegrand, anpicker, erooth, kakkoyun, lcosic, pkrupa, surbania
Target Milestone:	---
Target Release:	---
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-03-02 08:25:50 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 Federico Paolinelli 2021-02-17 14:55:46 UTC

Upgrade jobs from 4.7.0-rc.2 to 4.8.0-0.nightly are failing

Example: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.8-e2e-metal-ipi-upgrade/1361974381495980032

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.8-e2e-metal-ipi-upgrade/1361974381495980032

: [sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early] [Suite:openshift/conformance/parallel] expand_less 	5m2s
fail [k8s.io/kubernetes.0/test/e2e/framework/pod/resource.go:483]: failed to create new exec pod in namespace: e2e-test-prometheus-6sdx9
Unexpected error:
    <*errors.errorString | 0xc0003369b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

Comment 2 Sergiusz Urbaniak 2021-03-02 08:25:50 UTC

In that case closing out as a duplicate of 1929277.

*** This bug has been marked as a duplicate of bug 1929277 ***