OpenStack Compute (Nova)

log instance uuid in vmops.py when instances fail to spawn

Reported by Dan Prince on 2012-01-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Dan Prince

Bug Description

Update xenapi/vmops.py so that it logs the uuid instead of the instance ID when an instance fails to spawn:

Example (this is what currently happens):

2012-01-19 01:45:59,240 ERROR nova.virt.xenapi.vmops [-] instance 12345:
Failed to spawn

Dan Prince (dan-prince) on 2012-01-19
Changed in nova:
assignee: nobody → Dan Prince (dan-prince)
status: New → In Progress
importance: Undecided → Low
Brian Waldon (bcwaldon) on 2012-01-19
Changed in nova:
milestone: none → essex-3

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

commit c51c68c0163af9ae3e5795435a240589597c9648
Author: Dan Prince <email address hidden>
Date: Wed Jan 18 22:01:24 2012 -0500

    Log uuid when instances fail to spawn.

    Update xenapi/vmops.py so it logs the UUID instead of the instance ID
    when instances fail to spawn. Fixes LP bug #918497.

    Change-Id: Id7f41ccb79d22df5d10a5d6d9822ff65dd459056

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

Other bug subscribers