yahoo-eng-team team mailing list archive

[Kravchenko Pavel <1350790@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When you have on compute node unmanaged instance (not created with OS)
it would be expected that it's ignored by OpenStack, but in case when
it's name (e.g. instance-00000015) is same as the name openstack
allocated to the new instance it will act very bad.

At first attempt the deployment will fail, and the unmanaged instance
will be destroyed (probably because compute wants to remove leftovers of
the failed deployment). After that at the next attempt the instance will
be created.

At the end user will have a new instance managed by openstack that
replaced former unmanaged instance (has same name) in libvirt without
single notification to user.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Non managed Instance deleted during create

Status in OpenStack Compute (Nova):
  New

Bug description:
  When you have on compute node unmanaged instance (not created with OS)
  it would be expected that it's ignored by OpenStack, but in case when
  it's name (e.g. instance-00000015) is same as the name openstack
  allocated to the new instance it will act very bad.

  At first attempt the deployment will fail, and the unmanaged instance
  will be destroyed (probably because compute wants to remove leftovers
  of the failed deployment). After that at the next attempt the instance
  will be created.

  At the end user will have a new instance managed by openstack that
  replaced former unmanaged instance (has same name) in libvirt without
  single notification to user.

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