Duplicate attempts to destroy instance when calling os-stop and os-start

Bug #1917472 reported by Lee Yarwood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Wishlist
Unassigned

Bug Description

Description
===========

The libvirt driver's implementation of power_on currently uses _hard_reboot under the hood to recreate the underlying domain, volume connections and vifs. As part of this we attempt to destroy the domain but in the context of power_on that has already been handled by an earlier call to power_off. AFAICT the existing exception handling within destroy stops this ever being an issue but it is still inefficient and should be removed.

Steps to reproduce
==================

* Stop an instance
* Start an instance
* Note the duplicate attempts to destroy the instance

Expected result
===============

No attempt is made to destroy the instance while starting it.

Actual result
=============

An attempt to destroy the instance is made and while this doesn't result in an error it is inefficient.

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

   master

2. Which hypervisor did you use?
   (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
   What's the version of that?

   libvirt

2. Which storage type did you use?
   (For example: Ceph, LVM, GPFS, ...)
   What's the version of that?

   N/A

3. Which networking type did you use?
   (For example: nova-network, Neutron with OpenVSwitch, ...)

   N/A

Logs & Configs
==============

Tags: libvirt
Changed in nova:
status: New → Confirmed
importance: Undecided → Wishlist
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.