floatingip-create:Ignore floating_ip_address when specifying both floating_ip_address and subnet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Dongcan Ye |
Bug Description
When I created floating ip with "floating_
$neutron floatingip-create --floating-
Created a new floatingip:
+------
| Field | Value |
+------
| created_at | 2017-11-
| description | |
| fixed_ip_address | |
| floating_ip_address | 172.24.4.10 |
| floating_network_id | fa18e1d7-
| id | 4d6129a4-
| port_id | |
| project_id | f0f9361fbf8e495
| revision_number | 1 |
| router_id | |
| status | DOWN |
| tenant_id | f0f9361fbf8e495
| updated_at | 2017-11-
+------
This is my REQ:
DEBUG: keystoneauth.
And this is my RESP:
RESP BODY: {"floatingip": {"router_id": null, "status": "DOWN", "description": "", "tenant_id": "f0f9361fbf8e49
I think we should make sure the "floating_
Or we should report a error message when we set these parameters at the same time.
Changed in python-neutronclient: | |
assignee: | nobody → yanpuqing (ycx) |
affects: | python-neutronclient → neutron |
Changed in neutron: | |
status: | Incomplete → In Progress |
Using the openstackclient you should get a 403 error:
$ openstack floating ip create --floating- ip-address 172.24.4.99 public 1975-4aa5- b3ae-7930723e07 55)
Error while executing command: Forbidden (HTTP 403) (Request-ID: req-1167e309-
This is an admin-only operation as per the default entry in etc/policy.json:
"create_ floatingip: floating_ ip_address" : "rule:admin_only",
The admin can change that, which is why it isn't documented as admin-only.