Closed james-jra closed 6 years ago
Thanks. I am looking into this issue.
@james-jra
I have found the root-cause and will implement a fix. Will let you know when it is pushed. The fix will be in opx-nas-interface, not opx-cps.
Thanks, Garrick
@james-jra Update, I will push the changes soon. Been busy with other issues but I haven't forgotten you =)
@james-jra Issue is fixed with this push: https://review.openswitch.net/#/c/14731/1
Creating a LAG interface with a name that does not end in an integer fails and causes opx_nas_daemon to crash.
Note: The same behaviour is true even if we provide a LAG ID using
base-if-lag/if/interfaces/interface/id
Expected behaviour:
Reproduction
Create a LAG interface with a number at the end (succeeds):
Show opx_nas_daemon still up:
Create a LAG interface without a number in the name (fails):
Show opx_nas_daemon is down:
Diags
The following is the relevant extract from syslog: