yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52462
[Bug 1593522] [NEW] Error logging in compute manager _try_deallocate_network should include actual error
Public bug reported:
I hit this while trying to debug a tempest failure:
http://logs.openstack.org/01/327901/1/check/gate-tempest-dsvm-neutron-
full/8337f93/logs/screen-n-cpu.txt.gz#_2016-06-17_00_33_10_307
2016-06-17 00:33:10.307 24536 ERROR nova.compute.manager [req-f0f3cd57
-64ec-4c10-be5a-ae675278891a tempest-AutoAllocateNetworkTest-681217639
tempest-AutoAllocateNetworkTest-681217639] [instance:
13cb9234-1bc0-4e91-bd78-fd8b3c053ff7] Failed to deallocate network for
instance.
Which logs just this:
LOG.error(_LE('Failed to deallocate network for instance.'),
instance=instance)
We should actually log the exception here for context.
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Tags: compute logging usability
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1593522
Title:
Error logging in compute manager _try_deallocate_network should
include actual error
Status in OpenStack Compute (nova):
In Progress
Bug description:
I hit this while trying to debug a tempest failure:
http://logs.openstack.org/01/327901/1/check/gate-tempest-dsvm-neutron-
full/8337f93/logs/screen-n-cpu.txt.gz#_2016-06-17_00_33_10_307
2016-06-17 00:33:10.307 24536 ERROR nova.compute.manager [req-f0f3cd57
-64ec-4c10-be5a-ae675278891a tempest-AutoAllocateNetworkTest-681217639
tempest-AutoAllocateNetworkTest-681217639] [instance:
13cb9234-1bc0-4e91-bd78-fd8b3c053ff7] Failed to deallocate network for
instance.
Which logs just this:
LOG.error(_LE('Failed to deallocate network for instance.'),
instance=instance)
We should actually log the exception here for context.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1593522/+subscriptions
Follow ups