yahoo-eng-team team mailing list archive

[Mark McClain <1119409@xxxxxxxxxxxxxxxxxx>]

Changed Quantum status and removing the milestone.  The Quantum core
team believes that the server should continue to allow deletes when
these fields are set.  The preferred alternative is additional checks in
Horizon and/or the CLI to block deletion when the port is in-use.

** Changed in: quantum
    Milestone: grizzly-rc1 => None

** Changed in: quantum
   Importance: High => Medium

** Changed in: quantum
       Status: In Progress => Opinion

** Also affects: python-quantumclient
   Importance: Undecided
       Status: New

** Changed in: python-quantumclient
       Status: New => Triaged

** Changed in: python-quantumclient
   Importance: Undecided => Wishlist

** Changed in: quantum
       Status: Opinion => Invalid

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

Title:
  Delete is possible of an in-use port

Status in Python client library for Quantum:
  Triaged
Status in OpenStack Quantum (virtual network service):
  Invalid

Bug description:
  
  Running in a quantum-enabled devstack.

  Using Quantum, I created a network and subnet and then created a VM
  that used the network.

  I then deleted the port used by the VM - no error, and I end up
  getting a VM without an address :

  ubuntu at az3devstackvm2:/opt/stack/tempest2/tempest/tests/network$ nova list
  +--------------------------------------+-----------------------+--------+----------+
  | ID                                   | Name                  | Status | Networks |
  +--------------------------------------+-----------------------+--------+----------+
  | e43ec1a6-9499-4a7f-bbd0-fbecf6f3c115 | server-negtest-322040 | ACTIVE |          |
  +--------------------------------------+-----------------------+--------+----------+

  So far I've not found a way to re-attach the VM to my network.

  I'm unclear is this is a bug or a feature - however deleting an in-use network or subnet is trapped, so 
  I think this ought to be so also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-quantumclient/+bug/1119409/+subscriptions