Bug 1929748 - 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]
Summary: Upgrade from 4.7.0-rc2 to 4.8.0 fails [sig-instrumentation] Prometheus when i...
Keywords:
Status: CLOSED DUPLICATE of bug 1929277
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Lili Cosic
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-17 14:55 UTC by Federico Paolinelli
Modified: 2021-03-02 08:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-02 08:25:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1063 0 None open Bug 1929277: [master] jsonnet/prometheus.jsonnet: Apply openshift-user-critical class to cluster Prometheus 2021-02-17 17:05:10 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.