InstanceIP in public network
Bug #1368691 reported by
Babu Shanmugam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Unassigned | |||
OpenContrail |
Fix Committed
|
Undecided
|
Babu Shanmugam |
Bug Description
When a floating IP is reserved by a tenant, opencontrail allows it to be allocated as an InstanceIP.
Steps to reproduce;
1. Create a public network with router:external set to true
2. Create a subnet for the public network
3. Create a floating IP from the public network
4. Try launching a instance with net-id=<the public network>
5. The instance should not be launched, since the instance IP that the new instance will get is already reserved. But the instance will be launched with raising any error.
Changed in opencontrail: | |
assignee: | nobody → Babu Shanmugam (anbu-p) |
status: | New → In Progress |
Changed in juniperopenstack: | |
importance: | Undecided → High |
tags: | added: neutron |
Changed in opencontrail: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Reviewed: https:/ /review. opencontrail. org/2884 github. org/Juniper/ contrail- controller/ commit/ 1e55fc1ba46b51e d8eafb5a6a3e25e b02f54ce22
Committed: http://
Submitter: Zuul
Branch: master
commit 1e55fc1ba46b51e d8eafb5a6a3e25e b02f54ce22
Author: anbu <email address hidden>
Date: Wed Sep 10 10:20:31 2014 +0000
In an external network, even though a floatingIP is reserved, it can be created as an InstanceIP.
This patch corrects that bug
Closes-bug: #1368691
Change-Id: Ifc2203a05901f0 3a787fb3652c07d e0e09542017