ipvlan/macvlan driver: Incorrect Ipadrress assignment on container interface
Bug #1641537 reported by
vikas choudhary
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kuryr |
Fix Released
|
Undecided
|
vikas choudhary | ||
Bug Description
IP address is being assigned from host machine neutron port incorrectly.
| Changed in kuryr: | |
| assignee: | nobody → vikas choudhary (choudharyvikas16) |
| Changed in kuryr: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kuryr (master) | #1 |
| Changed in kuryr: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kuryr 0.2.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 19392738771dc4b
Author: vikaschoudhary16 <email address hidden>
Date: Mon Nov 14 08:17:52 2016 +0000
Fix container port ipaddress setting in ipvlan/macvlan drivers
Currently ipaddress is being set from nova instance port and thus
making vm ip and container ip same. Fix this by using container port
dict for getting container IP.
Another change is renaming 'nested_port', which is actually Nova
instance port, to 'vm_port', for the sake of avoiding ambiguity.
Change-Id: I9ea93c88c2889c
Closes-bug: #1641537