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

leafpath cannot be resolved for IETF model ietf-l3vpn-svc #115

Open
william-tremblay1 opened this issue Jul 19, 2024 · 2 comments
Open

leafpath cannot be resolved for IETF model ietf-l3vpn-svc #115

william-tremblay1 opened this issue Jul 19, 2024 · 2 comments

Comments

@william-tremblay1
Copy link

I'm trying to use freeconf with the ietf-l3vpn-svc model. I followed the Getting started guide (Python) to start a RESTCONF server with the model. After patching the models to fix #114, I get the following error:

ietf-l3vpn-svc/l3vpn-svc/sites/site/site-network-accesses/site-network-access/location-flavor/location/location-reference - leafref path cannot be resolved

The leafref in question is this line of the model. Pyang doesn't raise any errors when validating it, so I'm not sure if this is an issue with freeconf or the model itself.

Note that my YANG search path includes all the IETF RFC model collection (https://github.com/YangModels/yang/tree/main/standard/ietf/RFC).

@dhubler
Copy link
Collaborator

dhubler commented Jul 21, 2024 via email

@dhubler
Copy link
Collaborator

dhubler commented Jul 22, 2024

I investigated the YANG, this is in a choice/case with a when inside a grouping and a path of
"../../../locations/location/location-id";

This will take some investigation. Often I try to isolate the issue into a new, minimal yang file that still exhibits the error.

Past test files here
https://github.com/freeconf/yang/tree/master/parser/testdata

Would be able to tease out the error in a very simple test yang file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants