-
Notifications
You must be signed in to change notification settings - Fork 3
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
creating and removing connections eventually leads to error _unreserve_vlan Not implemented AssertionError #205
Comments
It may be related to #123 I noticed that pce/src/sdx_pce/topology/temanager.py Lines 91 to 98 in 5f40e1b
and the add_topology is only called when the SDX-LC is sending a topology for a unknown domain (not saved on the database). So if probably if you restart the SDX-Controller and sends again the topology for a domain (which was saved to the DB before the controller to restart), it seems like this issue could be triggered. This seems to happen at least the first time you restart SDX-Controller. |
Hello, team. Did you guys have the opportunity to check this issue? Ccing @YufengXin @sajith and @congwang09 I'm writing now because once again I was running tests and faced this issue. The SDX controller logs say this:
Which indicates the issue was missing vlan table on TENET domain. Looking on how TENET domain had its topology imported, we have:
As you can see above, the first topology event does not contains the full topology. Other nodes and links are added on subsequent events. This is normal behavior and can happen in real-world scenarios (beside tests like the one above). Since the |
Thanks, Italo, for this case, very good one! I added #123 to the meta issue. Sajith is in the process of managing these vlan related issues. |
Hi,
After creating and removing a few VLANs (one of them being the case reported on atlanticwave-sdx/sdx-controller#309), eventually we get the following error:
The request above was basically:
The text was updated successfully, but these errors were encountered: