OpenStack Compute (Nova)

compute service doesn't start with a missing libvirt instance.../disk

Reported by Pádraig Brady on 2012-03-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Pádraig Brady

Bug Description

One user reported on the Fedora test day that the compute service wouldn't start,
and this was due to a missing libvirt disk image.

Now that may have been due to running out of disk space,
or any of the issues addressed by these patches:
https://review.openstack.org/#change,5296
https://review.openstack.org/#change,5442

But I think it makes sense to program defensively for this case.

Patch coming up...

Changed in nova:
assignee: nobody → Pádraig Brady (p-draigbrady)
status: New → In Progress
Changed in nova:
importance: Undecided → Medium
tags: added: essex-rc-potential

Reviewed: https://review.openstack.org/5456
Committed: http://github.com/openstack/nova/commit/1d94d55775b78a5d37658bb641c225bc49510620
Submitter: Jenkins
Branch: master

commit 1d94d55775b78a5d37658bb641c225bc49510620
Author: Pádraig Brady <email address hidden>
Date: Fri Mar 16 16:00:43 2012 +0000

    allow the compute service to start with missing libvirt disks

    * nova/virt/libvirt/connection.py: Program defensively and handle
    the case of missing instance disks and log the error rather than
    propagating that exception up (which triggers nova.service to fail).
    * Fixes bug 957110

    Change-Id: I1a414f56661843ff6b886e6ebf6f614fcb5a5f31

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers