Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Find out a way to handle when switches haven't been connected yet #25

Open
viniarck opened this issue May 12, 2018 · 2 comments
Open

Find out a way to handle when switches haven't been connected yet #25

viniarck opened this issue May 12, 2018 · 2 comments
Milestone
2019.1b2

Comments

@viniarck
Copy link

If an EVC request comes before a switch is connected yet, currently only a 'Invalid uni_a' is logged as an error. This will be automatically solved when the schedule is properly running. Meanwhile, it should be nice to have a warning or something for this.

It's also related to improving error messages #22
@beraldoleal
Copy link
Member

Thanks @viniciusarcanjo to point this. There is any mention to this on our blueprints ?

@viniarck
Copy link
Author

I don't think so @beraldoleal. I've stumbled upon this recently.

@beraldoleal beraldoleal added this to the 2019.1b1 milestone Nov 6, 2018
@hdiogenes hdiogenes modified the milestones: 2019.1b1, 2019.1b2 Apr 2, 2019
@ajoaoff ajoaoff mentioned this issue Jun 8, 2021
Open
ajoaoff added a commit to ajoaoff/mef_eline that referenced this issue Jul 14, 2021
@ajoaoff
Change log level of mef_eline.storehouse
faa4978 
Some log messages were changed from info to debug,
disabling unnecessary messages
Fixes kytos#25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2019.1b2
Development

No branches or pull requests
3 participants
@hdiogenes @beraldoleal @viniarck