Public bug reported:
Some useful information about *why* a port binding failed should be
pushed up into ERROR level, since it has a useful error to help diagnose
the issue, and if someone doesn't have DEBUG level enabled they'd miss
it and wonder why it failed.
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Checking segment:
{'segmentation_id': None, 'physical_network': u'default', 'id':
u'eec249a0-829d-4a8c-a556-d04ffe7533ad', 'network_type': u'flat'} for mappings:
{} with network types: [u'vxlan', 'local', 'flat', 'vlan'] from (pid=13302)
check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:182
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Network
eec249a0-829d-4a8c-a556-d04ffe7533ad is connected to physical network default,
but agent vagrant-ubuntu-trusty-64.localdomain reported physical networks {}.
The physical network must be configured on the agent if binding is to succeed.
from (pid=13302) check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:208
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
** Affects: neutron
Importance: Undecided
Assignee: Sean M. Collins (scollins)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1523616
Title:
Failing to bind a port should report why it failed, even outside of
DEBUG level
Status in neutron:
In Progress
Bug description:
Some useful information about *why* a port binding failed should be
pushed up into ERROR level, since it has a useful error to help
diagnose the issue, and if someone doesn't have DEBUG level enabled
they'd miss it and wonder why it failed.
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Checking segment:
{'segmentation_id': None, 'physical_network': u'default', 'id':
u'eec249a0-829d-4a8c-a556-d04ffe7533ad', 'network_type': u'flat'} for mappings:
{} with network types: [u'vxlan', 'local', 'flat', 'vlan'] from (pid=13302)
check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:182
2015-12-07 17:41:00.584 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Network
eec249a0-829d-4a8c-a556-d04ffe7533ad is connected to physical network default,
but agent vagrant-ubuntu-trusty-64.localdomain reported physical networks {}.
The physical network must be configured on the agent if binding is to succeed.
from (pid=13302) check_segment_for_agent
/opt/stack/neutron/neutron/plugins/ml2/drivers/mech_agent.py:208
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
2015-12-07 17:41:00.585 ERROR neutron.plugins.ml2.managers
[req-4cade4e6-1586-4187-8af2-f9e57051a5bc None None] Failed to bind port
0e25c56e-2bcf-4079-bf6c-c28b72ab4ac0 on host
vagrant-ubuntu-trusty-64.localdomain
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1523616/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
