yahoo-eng-team team mailing list archive

[Artom Lifshitz <1930866@xxxxxxxxxxxxxxxxxx>]

It's a valid bug, but as ports are Neutron's responsibility, I'm not
sure what can be done in this case. Neutron is free to delete a port
without checking anything about the instance it's attached to. Perhaps
this can be changed to the Neutron component, to see if folks there have
an idea?

** Project changed: nova => neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1930866

Title:
  locked instance can be rendered broken by deleting port

Status in neutron:
  New

Bug description:
  'server lock' is indented to protect instance from simple mistakes
  (like removing the wrong instance, or shut-downing it). It does
  prevent shutdown, destruction and port detachment.

  But if port is removed via `openstack port delete` it silently get
  removed from locked instance, effectively, breaking it.

  Steps to reproduce:
  ```
  openstack server create foo
  openstack server lock foo
  openstack port delete {id of the port of the instance}
  ```

  Expected behavior: error message, rejecting to delete port, used by
  locked instance.

  Actual behavior: port is removed, leaving locked instance without
  network.

  
  I was able to reproduce it on nova 17.0.12, but newer versions may be affected too.

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