When create a fip with subnet_id and ip specified, the created fip won't be the ip specified
Bug #1719494 reported by
Yang Li
This bug report is a duplicate of:
Bug #1738612: Floating IP update breakes decomposed plugins.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Undecided
|
Unassigned |
Bug Description
When create a fip with subnet_id and ip option specified, the created fip won't be the ip specified, in the original code, it will be replaced with subnet_id, and it will confuse users.For example:
#neutron floatingip-create --floating-
then 10.10.0.2 was allocated, not 10.10.0.10
If only floating-ip-address is specified, the result is fine
#neutron floatingip-create --floating-
then 10.10.0.10 was allocated
Changed in neutron: | |
assignee: | nobody → Yang Li (yang-li) |
summary: |
When create a fip with subnet_id and ip specified, the created fip won't - be the ip specified, + be the ip specified |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
assignee: | Yang Li (yang-li) → Li Zhouzhou (lizhouzhou) |
To post a comment you must log in.
Fix proposed to branch: stable/pike /review. openstack. org/589030
Review: https:/