libvir: QEMU error : Domain not found in tempest gate

Bug #1182184 reported by Henry Gessau
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Hans Lindgren

Bug Description

When looking into the failure for
http://logs.openstack.org/29184/8/gate/gate-tempest-devstack-vm-quantum/23537/

[14:41:21] 19<sdague> HenryG: there it is - libvir: QEMU error : Domain not found: no domain with matching name 'instance-0000000b'
[14:41:38] 18<24sdague> 2013-05-20 15:47:13.480 DEBUG nova.openstack.common.lockutils [req-ddd6a6f2-7a52-49d3-8545-9e035aeb0134 demo demo] Got semaphore "3e9b1297-caf1-4daf-8127-919b8ba68fc4" for method "do_run_instance"... inner /opt/stack/new/nova/nova/openstack/common/lockutils.py:190
[14:41:38] 18<24sdague> libvir: QEMU error : Domain not found: no domain with matching name 'instance-0000000b'
[14:41:45] 18<24sdague> in n-cpu
[14:42:29] 18<24sdague> that's the domain fail that triggered the rest of the fails

Tags: libvirt
Revision history for this message
Kashyap Chamarthy (kashyapc) wrote :

Henry, can you please write a small note on how to trigger this error (w/o tempest) ? It'd be easier for triaging.

As a side note, please take a look this when filing bugs -- https://wiki.openstack.org/wiki/BugFilingRecommendations )

Revision history for this message
Kashyap Chamarthy (kashyapc) wrote :

Also,

  (1) Gerrit logs don't last forever, so it's not really ideal to point them when filing bugs.
  (2) Pasting IRC conversation without context isn't really much useful.

Thanks Flavio for pointing it out.

Please remember, these bugs are archived, and will be later referred.

Thanks.

Changed in nova:
status: New → Incomplete
Michael Still (mikal)
Changed in nova:
status: Incomplete → Triaged
importance: Undecided → Medium
status: Triaged → Incomplete
importance: Medium → Undecided
Revision history for this message
Hans Lindgren (hanlind) wrote :

These can be seen all over the compute logs of every recent tempest run.

Looks like something raises them for every instance being spawned. Mostly they appear to be cosmetic as tests succeed despite these errors.

Changed in nova:
assignee: nobody → Hans Lindgren (hanlind)
status: Incomplete → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/31001

Changed in nova:
status: Confirmed → In Progress
Hans Lindgren (hanlind)
tags: added: libvirt
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/31001
Committed: http://github.com/openstack/nova/commit/eb40b5ab13d11e773eb0c78084e9935fcd5a6552
Submitter: Jenkins
Branch: master

commit eb40b5ab13d11e773eb0c78084e9935fcd5a6552
Author: Hans Lindgren <email address hidden>
Date: Wed May 29 22:59:41 2013 +0200

    Stop libvirt errors from outputting to strerr

    When a libvirt error happens, the default is to output to stderr. This
    behavior can be omitted by registering a new error that simply passes
    without doing anything.

    Resolves bug 1182184.

    Change-Id: If946f9d05388c93c0630d454e5ca3b6625bb14f9

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → havana-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: havana-2 → 2013.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.