You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cps_get_oid.py if/interfaces/interface 'if/interfaces/interface/name=e101-001-0' should return EXACTLY what is presently being returned by cps_get_oid.py dell-base-if-cmn/if/interfaces/interface 'if/interfaces/interface/name=e101-001-0'
Instead it returns nothing.
This violates the concept of augmentation as described in RFC6020, RFC7950 (yang) and is incompatible with well established representations of RFC8040 (restconf) and 6241 (netconf)
What is the problem you are reporting - Fundamental design fault
Do you have a use case including examples? - yes, stated
Is there a blocker? (Y/N), and include the reasoning if it is a blocker. - it is a blocker for implementing restconf, netconf or any other interop natively without presenting a "hacked" model to the consumer
OPX version that you are using (latest or specific version) - all up to head of tree
Which platform are you using? - Irrelevant as bug is on all platforms
How frequently is the bug reproducible (always, intermittently, and so on)? - Always
Include the steps to reproduce the problem - Just read the rfc please
Include any logs (journalctl -f, opx-show-version, opx-show-system-status, and so on). - not applicable
Have you found a workaround that resolves your problem? - none
Dell-base-common augments ietf-interfaces.
The expectation would be that the keys should still be from ietf-interfaces instead of dell-base-common. Not the case.
Additionally, to add to the confusion, while the keys are under dell-base-cmn, the data is still under if/ +/- augmentations.
This makes the whole interface tree non-interoperable versus upstream implementations without remapping and re-parenting it for presentation.
The text was updated successfully, but these errors were encountered: