-
Notifications
You must be signed in to change notification settings - Fork 8
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
enable switch and all interfaces on a switch eventually is not persisted #92
Comments
@italovalcy, thanks for reporting this and proving the topology and scripts. I'm under the impression that at the time when all the interfaces of the switches got enabled the interfaces hadn't been created yet, so it seems that OF port description hasn't been received at that point since calling Could you please double check if adding a wait in the script before enabling the interfaces, or alternatively a more robust keep checking if the expected interfaces have already been created before enabling them? |
Hi @viniarck ! thanks a lot for the information! Yes, I agree with you about returning 404 if there are no interface to be enabled. |
Sounds good, @italovalcy . I've removed the other labels from this issue and let's address this as an enhancement then. In addition to 404, I believe it could also return in the body a list of interface ids that it enabled, that way the client can also double check which ones were enabled. wdyt? And then we let clients to be aware in the release notes in a future version that they can double check the body to figure out which ones were enabeld. Same approach for disabling all interfaces too. |
Hi,
Doing a few performance tests on Kytos I found a side effect of sometimes the topology doesn't converge, meaning: not all the links are actually discovered by Kytos.
How to reproduce?
Expected behavior:
Actual behavior:
POST /topology/v3/interfaces/switch/$sw/enable
:The text was updated successfully, but these errors were encountered: