Bug 2053307 - allow inexact matches for disruption and alert data
Summary: allow inexact matches for disruption and alert data
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Framework
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: David Eads
QA Contact:
URL:
Whiteboard:
Depends On: 2053143
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-10 22:20 UTC by OpenShift BugZilla Robot
Modified: 2022-02-28 18:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-28 18:24:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26836 0 None open [release-4.10] bug 2053307:allow inexact matches for disruption data 2022-02-10 22:20:54 UTC

Description OpenShift BugZilla Robot 2022-02-10 22:20:44 UTC 
+++ This bug was initially created as a clone of Bug #2053143 +++

This will help alleviate problems like https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/1302/pull-ci-openshift-cluster-network-operator-master-e2e-agnostic-upgrade/1491351105987153920 where we don't have exact data matches.
Note You need to log in before you can comment on or make changes to this bug.