yahoo-eng-team team mailing list archive

[Joe Gordon <1270355@xxxxxxxxxxxxxxxxxx>]

00:25 < jog0> sdague: not sure how to treat this bug 
              https://bugs.launchpad.net/nova/+bug/1270355
00:25 < jog0> we turned off fail on stacktrace right?
00:25 < jog0> this looks like its related to debug forlibvirt
00:29 < sdague> jog0: looking
00:30 < sdague> jog0: so we've turned enforcement back off
00:30 < jog0> sdague: and the libvrirt debug logs?
00:30 < sdague> that's in gate
00:30 < jog0> looks like an enforcment glitch
00:30 < sdague> yeh
00:30 < jog0> so move to tempest? I don't think this is a nova bug 
00:31 < sdague> yeh
00:31 < sdague> assign to dkranz
00:31 < sdague> he'll need to throw it on the whitelist


** Also affects: tempest
   Importance: Undecided
       Status: New

** Changed in: tempest
     Assignee: (unassigned) => David Kranz (david-kranz)

** Changed in: nova
       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:
  New

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