yahoo-eng-team team mailing list archive

[Takashi NATSUME <natsume.takashi@xxxxxxxxxxxxx>]

Public bug reported:

Currently, the details of libvirt events are not outputted to the log when nova-compute handles libvirt events.
The details of libvirt events should be outputted to the log for troubleshooting.

By the following blue print, nova has been able to catch libvirt events
and synchronize the VM state with 'actual' state immediately.

Compute Driver Events
https://blueprints.launchpad.net/nova/+spec/compute-driver-events

When nova-compute handles libvirt events, it outputs which libvirt events(EVENT_LIFECYCLE_STARTED, EVENT_LIFECYCLE_STOPPED, EVENT_LIFECYCLE_PAUSED, EVENT_LIFECYCLE_RESUMED) are received.
But the details(cause/reason) of libvirt events are not outputted.
For example, in the case of VIR_DOMAIN_EVENT_STOPPED(=EVENT_LIFECYCLE_STOPPED), the details are as follows(*1).

VIR_DOMAIN_EVENT_STOPPED_SHUTDOWN = 0 Normal shutdown
VIR_DOMAIN_EVENT_STOPPED_DESTROYED = 1 Forced poweroff from host
VIR_DOMAIN_EVENT_STOPPED_CRASHED = 2 Guest crashed
VIR_DOMAIN_EVENT_STOPPED_MIGRATED = 3 Migrated off to another host
VIR_DOMAIN_EVENT_STOPPED_SAVED = 4 Saved to a state file
VIR_DOMAIN_EVENT_STOPPED_FAILED = 5 Host emulator/mgmt failed
VIR_DOMAIN_EVENT_STOPPED_FROM_SNAPSHOT = 6 offline snapshot loaded
VIR_DOMAIN_EVENT_STOPPED_LAST = 7

*1: http://libvirt.org/html/libvirt-libvirt.html

If the details of libvirt events are outputted to the log, it will be
useful in troubleshoot.

** Affects: nova
     Importance: Undecided
     Assignee: Takashi NATSUME (natsume-takashi)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Takashi NATSUME (natsume-takashi)

-- 
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/1311082

Title:
  The details of libvirt events are not outputted to the log when nova-
  compute handles libvirt events.

Status in OpenStack Compute (Nova):
  New

Bug description:
  Currently, the details of libvirt events are not outputted to the log when nova-compute handles libvirt events.
  The details of libvirt events should be outputted to the log for troubleshooting.

  By the following blue print, nova has been able to catch libvirt
  events and synchronize the VM state with 'actual' state immediately.

  Compute Driver Events
  https://blueprints.launchpad.net/nova/+spec/compute-driver-events

  When nova-compute handles libvirt events, it outputs which libvirt events(EVENT_LIFECYCLE_STARTED, EVENT_LIFECYCLE_STOPPED, EVENT_LIFECYCLE_PAUSED, EVENT_LIFECYCLE_RESUMED) are received.
  But the details(cause/reason) of libvirt events are not outputted.
  For example, in the case of VIR_DOMAIN_EVENT_STOPPED(=EVENT_LIFECYCLE_STOPPED), the details are as follows(*1).

  VIR_DOMAIN_EVENT_STOPPED_SHUTDOWN = 0 Normal shutdown
  VIR_DOMAIN_EVENT_STOPPED_DESTROYED = 1 Forced poweroff from host
  VIR_DOMAIN_EVENT_STOPPED_CRASHED = 2 Guest crashed
  VIR_DOMAIN_EVENT_STOPPED_MIGRATED = 3 Migrated off to another host
  VIR_DOMAIN_EVENT_STOPPED_SAVED = 4 Saved to a state file
  VIR_DOMAIN_EVENT_STOPPED_FAILED = 5 Host emulator/mgmt failed
  VIR_DOMAIN_EVENT_STOPPED_FROM_SNAPSHOT = 6 offline snapshot loaded
  VIR_DOMAIN_EVENT_STOPPED_LAST = 7

  *1: http://libvirt.org/html/libvirt-libvirt.html

  If the details of libvirt events are outputted to the log, it will be
  useful in troubleshoot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1311082/+subscriptions