Bug 1805230 - Reenable monitoring tests in CI
Summary: Reenable monitoring tests in CI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: David Taylor
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1800748
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-20 14:21 UTC by David Taylor
Modified: 2020-05-13 21:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1800748
Environment:
Version: 4.4.0-0.ci-2020-02-07-125353 Cluster ID: 02913ce8-f389-409b-a79d-8d6ecdf40695 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Last Closed: 2020-05-13 21:59:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4384 0 None closed [release-4.4] Bug 1805230: Re-enable monitoring tests in CI 2020-04-20 16:07:27 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 21:59:41 UTC

Description David Taylor 2020-02-20 14:21:31 UTC 
+++ This bug was initially created as a clone of Bug #1800748 +++

Now that bug 1794885, we can reenable the console monitoring tests in CI. They were disabled by this commit:

https://github.com/openshift/console/pull/4065/commits/ee6cd20fca8907a318d5494ed9c1576d9971ae28

--- Additional comment from Samuel Padgett on 2020-02-11 18:14:40 UTC ---

Assigning to Dave because the Alertmanager tests are failing:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_console/4255/pull-ci-openshift-console-master-e2e-gcp-console/11842
Comment 3 Yanping Zhang 2020-02-24 09:18:39 UTC 
Checked in ci/prow/e2e-gcp-console job, the Alertmanager tests are added back. So move the bug to Verified.
Comment 5 errata-xmlrpc 2020-05-13 21:59:40 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581
Note You need to log in before you can comment on or make changes to this bug.