Inconsistent simple_ip_management behavior with Neutron
Bug #1226003 reported by
Sandro Mathys
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Akihiro Motoki |
Bug Description
Neutron does not (yet?) support the mechanism behind simple_
Thus, the behavior is highly inconsistent, if Neutron is used for Networking and simple_
Changed in horizon: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in horizon: | |
assignee: | Timur Sufiev (tsufiev-x) → nobody |
status: | In Progress → Triaged |
Changed in horizon: | |
milestone: | none → queens-3 |
Changed in horizon: | |
milestone: | queens-3 → queens-rc1 |
Changed in horizon: | |
milestone: | queens-rc1 → queens-rc2 |
To post a comment you must log in.
Agreed, this is inconsistent and should be fixed. If simple_associate is not supported, simple_disassociate probably shouldn't be enabled either.
https:/ /github. com/openstack/ horizon/ blob/master/ openstack_ dashboard/ dashboards/ project/ instances/ tables. py#L375 /github. com/openstack/ horizon/ blob/master/ openstack_ dashboard/ dashboards/ project/ instances/ tables. py#L404
https:/
Additionally, the docs as of now only document the effect of "simple_ ip_management" in terms of associating IPs; what it does with disassociation should also be explained: that is, "Simple Disassociation" means both disassociating *and* releasing the floating IP in one click.
http:// docs.openstack. org/developer/ horizon/ topics/ settings. html#simple- ip-management