This is actually working as designed. Manually assigned floating IPs can
be deleted in a single go, auto assigned ones must be disassociated
first. Changing this default would probably *break* lots of users, so I
don't think we should.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1437141
Title:
nova floating-ip-delete should warn or refuse if an IP is still
associated
Status in OpenStack Compute (Nova):
Opinion
Bug description:
Running 'nova floating-ip-delete <IP>' will happily delete IP
addresses that are associated with currently-running instances.
It would be safer if the user were required to either disassociate
them from the instance before being permitted to delete them, or to
pass a --force flag or similar.
Version installed is python-novaclient 1:2.17.0-0ubuntu1~cloud0
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1437141/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
