-
Notifications
You must be signed in to change notification settings - Fork 127
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
Ligato will add unrelated config on restart #1800
Comments
Can you run |
Will do! |
Ok, done some more investigating I have been using the rest api instead for these test. This flow will cause the issues:
At this point, using retreive will cause a crash
config get will give this:
Worth mentioning, retrieve never works for us:
Another thing worth mentioning, we run vpp on the host, mounting the sockets into the vpp-agent container. Could it be compability issues? |
Hello,
We noticed that for some reason ligato will add breaking config once restarted.
On the first apply of config, via etcd, it will work correctly. But if we restart ligato, additional entries will be added that break our env.
config, which is applied via etcd using a script:
Route entry on first apply:
Route entry on ligato restart (docker restart ligato):
Note the added arp entry
Using goVPP directly and adding the route twice seems to work, indicating it is something wrong in ligato when constructing models.
Any idea where to look for the issue?
The text was updated successfully, but these errors were encountered: