But if we have no Error message for end user when trying to delete
incorrect fixed IP, it looks confusing and inaccurate. What about adding
a microversion with support of IP validation before RPC request
sending?
** Changed in: nova
Status: Invalid => 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/1534186
Title:
Nova remove-fixed-ip doesn't return an error message when incorrect
fixed IP is removed
Status in OpenStack Compute (nova):
New
Bug description:
Reproduce steps:
1. Create net01: net01__subnet, 192.168.1.0/24:
neutron net-create net01
neutron subnet-create net01 192.168.1.0/24 --enable-dhcp --name net01__subnet
2. Boot instance vm1 in net01:
NET_ID=$(neutron net-list | grep 'net01' | awk '{print $2}')
nova boot --flavor m1.micro --image TestVM --nic net-id=$NET_ID
--security-groups default vm1
3. Note the fixed IP of vm1:
nova show vm1 | grep network
| net01 network | 192.168.1.36
|
4. Try to remove incorrect fixed IP from vm1:
nova remove-fixed-ip vm1 192.168.1.37
Expected result:
A message appears informing that the operation was not correct
Actual result:
Nothing happens and displayed
Nova version - http://paste.openstack.org/show/483603/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1534186/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp