[Bug 1298061] Re: nova should allow evacuate for an instance in the Error state

[Seyeong Kim]

ii  nova-common                          1:2014.1.5-0ubuntu1.6                 all          OpenStack Compute - common files
ii  nova-compute                         1:2014.1.5-0ubuntu1.6                 all          OpenStack Compute - compute node base
ii  nova-compute-kvm                     1:2014.1.5-0ubuntu1.6                 all          OpenStack Compute - compute node (KVM)
ii  nova-compute-libvirt                 1:2014.1.5-0ubuntu1.6                 all          OpenStack Compute - compute node libvirt support
ii  python-nova                          1:2014.1.5-0ubuntu1.6                 all          OpenStack Compute Python libraries


deployed openstack-base with juju on maas

created trusty-test instance

maas-node-02(source) - stopped nova-compute service
maas-node-03(destination)

nova evacuate --password 123qwe trusty-test maas-node-03

then got password as output

Thanks.


** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1298061

Title:
  nova should allow evacuate for an instance in the Error state

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive icehouse series:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

   * Instances in error state cannot be evacuated.

  [Test Case]

   * nova evacuate <error_state_instance> <another_compute_host>
   * nova refuses to evacuate the instance because of its state

  [Regression Potential]

   * Cherry picked from upstream
     - removed unnecessary argument passing
     - add allowing ERROR state before evacuating.
   * actually, in code, added one parameter, and removed unused one.
     so very low regression possibility.
   * Tested on juju+maas test env.
   * Passed tempest smoke tests locally.

  Note: one simple way to put an instance into error state is to
  directly change its database record, for example "update instances set
  vm_state='error' where uuid='XXXXXXXX'"

  We currently allow reboot/rebuild/rescue for an instance in the Error
  state if the instance has successfully booted at least once.

  We should allow "evacuate" as well, since it is essentially a
  "rebuild" on a different compute node.

  This would be useful in a number of cases, in particular if an initial
  evacuation attempt fails (putting the instance into the Error state).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1298061/+subscriptions