libvirt ERROR in n-cpu log after successful tempest run
Bug #1243823 reported by
David Kranz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned |
Bug Description
This is happening a lot. Example: http://
2013-10-23 02:15:42.433 27883 INFO nova.virt.
2013-10-23 02:15:42.435 ERROR nova.virt.
tags: | added: libvirt |
summary: |
- libvert ERROR in n-cpu log after successful tempest run + libvirt ERROR in n-cpu log after successful tempest run |
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
This is what it seems to be hitting:
https:/ /github. com/openstack/ nova/blob/ master/ nova/virt/ libvirt/ driver. py#L809
I think it's trying to "destroy" (i.e. "force stop" in libvirt's parlance) a non-existent domain -- which is not really catastrophic, and that's why Tempest runs must be succeeding?