fixed ip gets assigned when a port is created with no fixed ip
Bug #1617409 reported by
Sridhar Venkat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Manikantha Srinivas Tadi | ||
neutron |
Fix Released
|
High
|
Carl Baldwin |
Bug Description
When a neutron port is created with no fixed ip, and bound to a nova instance, a random IP is automatically picked up from subnet pool and assigned.
Port request body :
port_req_body
{'port': {'network_id': u'b3bfb646-
After it is bound to a nova instance, it gets an ip associated with it. From neutron port-show :
| fixed_ips | {"subnet_id": "90f2afbc-
This appears to be a problem due to changes in newton. This behavior was not there in mitaka.
Changed in nova: | |
assignee: | nobody → Manikantha Srinivas Tadi (manikantha-tadi) |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Medium → High |
To post a comment you must log in.
This is most likely not something that Nova is doing, but rather something Neutron is doing when the port is created, based on the type of neutron setup you have.