ml2 provides no information if there is no suitable mech_driver found during port binding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
If there is no suitable mech driver found, ML2 just make port bind_failed and write uninformative message in the log:
2017-01-12 13:56:46.691 3889 ERROR neutron.
I think it should report reason for this to admins more clearly, saying that no mechanism driver found to bind port.
In my case it was: INFO neutron.
version: 2:9.0.0-
summary: |
ml2 provides no information if there is no suitable mech_driver found + during port binding |
Changed in neutron: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
I'm going to close this bug since at least in this case there should have been three related info messages:
Loaded mechanism driver names: []
Registered mechanism drivers: []
No mechanism drivers provide segment reachability information for agent scheduling.
I would also not be opposed to someone adding code to catch that case and even do something similar to what _driver_not_found() does and SystemExit() - it anyone has the time for that please re-open the bug. Thanks.