When comparing attributes from multiple sources, violations thrown do not accurately show the issue.

Description

Our current deployment has the following information: 

AAI

pnf1

  

pinterface1

pinterface2

uuid: id1

uuid: id2

name: name1

name: name2

ND

pnf1

 

pinterface1

pinterface2

uuid: id1

uuid: id2

name: name1

name: abcde

 

The expectation is to compare name1 between the 2 contexts and name2 and abcde between the 2 contexts.  A violation then should be raised on the name on pinterface2.

 

However, today, it is basically taking all the names across AAI and all the names against ND (for pinterface) and just running a compare.  This could mean that nd.pinterface2.name=abcde can be compared against aai.pinterface1.name.  

 

This throws a violation that is not correct, and the message is mis-leading; 

"severity": "ERROR", "violationType": "Rule", "validationRule": "Attribute-comparison", "errorMessage": "Error found with attribute(s) and values: [lockedBoolean:[false, true], name:[abcde, name1]]",

Environment

None

Activity

Show:

Former user December 9, 2021 at 4:20 PM

This issue belongs to an unmaintained project and hast not been updated in 18 months or more, so closing.

Former user May 6, 2020 at 1:52 PM

Remove Fix Version since no more activity on this project - to be documented in the Frankfurt release as known restriction

Former user July 17, 2019 at 1:33 PM

Good afternoon - I have updated the FixVersion as suggested.

Former user July 17, 2019 at 12:37 PM
Edited

, unfortunately we have no plan and resources to work on this in the El Alto timeframe.  May I take it out of the El Alto release?  And this is POMBA related.

Former user March 18, 2019 at 5:37 PM

I cam seeing similar behavior in port-description as well. 

 

Won't Do

Details

Assignee

Reporter

Affects versions

Priority

Created March 14, 2019 at 8:49 PM
Updated August 12, 2023 at 3:50 AM
Resolved December 9, 2021 at 4:20 PM