So our enforcement strategy for tracking failures and traces in the logs
has changed since this was filed and this bug isn't valid any more
because of the change. But this looked liked a whitelist matching issue
when it still applied.
** Changed in: tempest
Status: New => Invalid
--
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/1270355
Title:
ERROR nova.virt.libvirt.driver virNetMessageFree:XX msg=0x<number>
found in error logs of check job
Status in OpenStack Compute (Nova):
Invalid
Status in Tempest:
Invalid
Bug description:
2014-01-18 02:05:31.528 | Checking logs...
2014-01-18 02:05:32.316 | Log File: n-cpu
2014-01-18 02:05:32.317 | 2014-01-18 01:45:00.948 26765 ERROR
nova.virt.libvirt.driver [-] [instance:
5fcba897-e4df-4e75-8a63-d08f136a5e0a]2014-01-18 01:45:00.948+0000: 29523: debug
: virNetMessageFree:75 : msg=0x7f398c001690 nfds=0 cb=(nil)
2014-01-18 02:05:32.317 |
2014-01-18 02:05:35.968 | Logs have errors
2014-01-18 02:05:35.968 | FAILED
See: http://logs.openstack.org/47/65347/6/check/check-tempest-dsvm-
full/8f71a0b/console.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1270355/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
