Loading...

XML

Word

Printable

Release Note Status:
Done
Release Note Type:
Bug Fix
Release Note Text:

Hide
In some cases, notably the PtpConfig objects in the Telco RAN reference, the algorithm used to differentiate between multiple matching templates was not selecting the nearest match, but arbitrarily selecting one match. The new algorithm properly detects the nearest match during template correlation.

Show
In some cases, notably the PtpConfig objects in the Telco RAN reference, the algorithm used to differentiate between multiple matching templates was not selecting the nearest match, but arbitrarily selecting one match. The new algorithm properly detects the nearest match during template correlation.

This is a clone of issue ~~OCPBUGS-53199~~. The following is the description of the original issue:
—
Description of problem:

Our one-of match intentionally uses a fuzzy-match to differentiate between multiply-matching objects, but it sometimes gets things wrong.

Version-Release number of selected component (if applicable):

4.18

How reproducible:

100%

Steps to Reproduce:

    1. Use a valid Dual-card PtpConfig
    2. Introduce a one difference
    3. Run cluster-compare with the RAN reference

Actual results:

The final comparison does not match the dual-card config, but the single-card config

Expected results:

We should match against the dual-card config because it is semantically closer to the dual-card config

clones

OCPBUGS-53199 cluster-compare cannot differentiate between multiply-matched templates

is blocked by

OCPBUGS-53199 cluster-compare cannot differentiate between multiply-matched templates

links to