Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation for port Override policy DN #88

Closed
kuskovoi opened this issue Mar 8, 2024 · 0 comments · Fixed by #124
Closed

Validation for port Override policy DN #88

kuskovoi opened this issue Mar 8, 2024 · 0 comments · Fixed by #124
Assignees

Comments

@kuskovoi
Copy link

kuskovoi commented Mar 8, 2024

There was strict check implemented on PD as part of CSCwh68103 validating the syntax of port Override policy ( infraRsHPathAtt ) if any. Usually it's used to define port description. There was no validation before so there might be objects in the model with incorrect syntax which are not actively used but just present in DB.

With the new validation it breaks policy download during clean-reload or upgrade, policyelem process on the Leaf is hitting exception in that case.

The examples of DN syntax for infraRsHPathAtt class objects are here:

"dn" : "uni/infra/hpaths-101_eth101_1_1/rsHPathAtt-[topology/pod-1/paths-101/extpaths-101/pathep-[eth1/1]]" --- CORRECT

"dn": "uni/infra/hpaths-101_eth101_1_1/rsHPathAtt-[topology/pod-1/paths-101/pathep-[eth101/1/1]]" --- INCORRECT

@monrog2 monrog2 self-assigned this May 15, 2024
@monrog2 monrog2 linked a pull request May 15, 2024 that will close this issue
takishida pushed a commit that referenced this issue May 17, 2024
* invalid_fex_rs_check + tests

* docs + check doc link

* fix bugId in doc

* remove `check` from title
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants