Improve logging for port binding
Bug #1543510 reported by
Rossella Sblendido
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
Rossella Sblendido | ||
Bug Description
When the port binding fails is very hard to understand what's going on. Logs need to be improved and some duplicate log needs to be removed.
| Changed in neutron: | |
| importance: | Undecided → Low |
| Changed in neutron: | |
| assignee: | nobody → Rossella Sblendido (rossella-o) |
| status: | New → In Progress |
| Changed in neutron: | |
| milestone: | none → mitaka-rc1 |
| importance: | Low → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c6db32e8a713f24
Author: rossella <email address hidden>
Date: Thu Feb 4 12:37:14 2016 +0100
Improve logging for port binding
When binding a port fails, it's really hard right now to
understand the reasons of the failure, unless the log level
is set to debug. In addition to that many log statement
are duplicated.
The goal of this patch is to solve these problems.
Closes-bug: #1543510
Change-Id: I262973126e8ca5