Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1827123

Summary: [buildcop][4.5 ci] Prometheus when installed on the cluster should have a AlertmanagerReceiversNotConfigured alert in firing state
Product: OpenShift Container Platform Reporter: Tomas Smetana <tsmetana>
Component: MonitoringAssignee: Pawel Krupa <pkrupa>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone: ---   
Target Release: 4.5.0   
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: 2020-04-24 07:27:03 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 Tomas Smetana 2020-04-23 09:59:19 UTC 
Encountered following failure in 4.5 CI:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.5/1627

[sig-instrumentation] Prometheus when installed on the cluster should have a AlertmanagerReceiversNotConfigured alert in firing state [Suite:openshift/conformance/parallel] expand_less 	1m38s
fail [github.com/openshift/origin/test/extended/prometheus/prometheus_builds.go:167]: Expected
    <map[string]error | len:1>: {
        "ALERTS{alertstate=\"firing\",alertname=\"AlertmanagerReceiversNotConfigured\"} == 1": {
            s: "promQL query: ALERTS{alertstate=\"firing\",alertname=\"AlertmanagerReceiversNotConfigured\"} == 1 had reported incorrect results:\n[]",
        },
    }
to be empty
Comment 3 Pawel Krupa 2020-04-24 07:27:03 UTC 
More detailed reason is in https://bugzilla.redhat.com/show_bug.cgi?id=1827489. Closing this one as duplicate

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