Won't Do
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Labels
Affects versions
Priority
High
Details
Details
Assignee
Former user
Former user(Deactivated)Reporter
Former user
Former user(Deactivated)Labels
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
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]]",