We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
veth links need special handling for add and delete as they are create with single command and deleted by single command,
if we create veth10 --> veth20 using the command:
veth10
veth20
ip -n red link add veth10 type veth peer name veth20
we will have the device leaf set to the peer link, this create circular dependency issue in the yang module.
device
if we try to delete veth10 for instance, it will complain that veth20 has leafref to the veth you are trying to delete.
if we try to delete both veths iproute2-sysrepo will crash due to max recurision depth at add_node_dependencies().
iproute2-sysrepo
add_node_dependencies()
** suggested solution: is to have veth link as separate list inside links container, and set the device type to string instead of leafref.
links
leafref
The text was updated successfully, but these errors were encountered:
No branches or pull requests
veth links need special handling for add and delete as they are create with single command and deleted by single command,
if we create
veth10
-->veth20
using the command:we will have the
device
leaf set to the peer link, this create circular dependency issue in the yang module.if we try to delete
veth10
for instance, it will complain thatveth20
has leafref to the veth you are trying to delete.if we try to delete both veths
iproute2-sysrepo
will crash due to max recurision depth atadd_node_dependencies()
.** suggested solution:
is to have veth link as separate list inside
links
container, and set thedevice
type to string instead ofleafref
.The text was updated successfully, but these errors were encountered: