Bug 2053307

Summary: allow inexact matches for disruption and alert data
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Test FrameworkAssignee: David Eads <deads>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10CC: dgoodwin
Target Milestone: ---   
Target Release: 4.10.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: 2022-02-28 18:24:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2053143    
Bug Blocks:    

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.