neutron unable to create l3 interface from private subnets once external gateway is set
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R1.1 |
Fix Committed
|
High
|
Rudra Rugge | |||
| Trunk |
Fix Committed
|
High
|
Rudra Rugge | |||
Bug Description
From: Rahul Sharma <email address hidden>
Date: Thursday, July 31, 2014 at 11:56 PM
To: Contrail Systems Configuration Team <email address hidden>
Cc: Vedamurthy Ananth Joshi <email address hidden>
Subject: Router Interface add fails
Not sure if Vedu is already tracking this, but I could not get an interface on the l3 router. Do we need any quotas or any other config for this to work?
Build is
2014-07-31 23:52:53.740 ERROR [neutron.
Traceback (most recent call last):
File "/usr/lib/
result = method(
File "/usr/lib/
return getattr(
File "/usr/lib/
obj_
File "/usr/lib/
raise error_class(
ContrailService
In neutron plugin in API server:
u'uuid': u'd224913e-
Notification Message: {u'oper': u'UPDATE',
u'type': u'access-
u'uuid': u'697c2a23-
Notification Message: {u'oper': u'UPDATE',
u'type': u'project',
u'uuid': u'3670f215-
<pre>Traceback (most recent call last):
File "/usr/lib/
subnet_
File "/usr/lib/
'name': ''})
File "/usr/lib/
self.
File "/usr/lib/
bottle.
File "/usr/lib/
raise HTTPError(code, text)
HTTPError
</pre>
| Rahul (rahuls) wrote | #1 |
| tags: | added: neutronapi |
| information type: | Proprietary → Public |
| Changed in juniperopenstack: | |
| assignee: | Sachin Bansal (sbansal) → Rudra Rugge (rudrarugge) |
| Changed in juniperopenstack: | |
| milestone: | r1.10-fcs → none |
| tags: | added: releasenote |
From: Pedro Marques <email address hidden>
Date: Friday, August 1, 2014 at 1:52 AM
To: Vedamurthy Ananth Joshi <email address hidden>
Cc: Rahul Sharma <email address hidden>, Sachin Bansal <email address hidden>, Contrail Systems Configuration Team <email address hidden>
Subject: Re: Creation of a svc_snat n/w with l3 router
For 1.1 we are supporting neutron router set-gateway to external network (That is how you turn on source-nat).
Pedro.
On Jul 31, 2014, at 1:05 PM, Vedamurthy Ananth Joshi <email address hidden> wrote:
Sachin,
We had this bug for gateway.. https:/
I see that it is marked fixed. Does it mean gateway is supported now?…Could you please clarify ?
From: Rahul Sharma <email address hidden>
Date: Friday, August 1, 2014 at 1:31 AM
To: Vedamurthy Joshi <email address hidden>, Sachin Bansal <email address hidden>
Cc: Contrail Systems Configuration Team <email address hidden>
Subject: Re: Creation of a svc_snat n/w with l3 router
If we don’t support external gateway then why are we using “router:external” on networks? Do you have a list of what we support and what we don’t as per the Specs/API’s?
External networks (external-net)
List networks
Show network details
Create network
Update network
The external network extension is used to specify whether the network is external or not. This information is used by Layer-3 network (router) extension. External networks are connected to a router's external gateway and host floating IPs.
The external network extension adds the router:external attribute to the network resource.
Table 4.3. Network Attributes
Attribute Type Required CRUD[a] Default Value Validation Constraints Notes
router:external Bool No CRU False { True | False } Specifies whether the network is an external network or not.
[a] C. Use the attribute in create operations.
R. This attribute is returned in response to show and list operations.
U. You can update the value of this attribute.
D. You can delete the value of this attribute.
From: Vedamurthy Ananth Joshi <email address hidden>
Date: Friday, August 1, 2014 at 1:19 AM
To: Rahul Sharma <email address hidden>, Sachin Bansal <email address hidden>
Cc: Contrail Systems Configuration Team <email address hidden>
Subject: Re: Creation of a svc_snat n/w with l3 router
Looks like you are also configuring external gateway.. Per Sachin, we don’t support this.
From: Rahul Sharma <email address hidden>
Date: Friday, August 1, 2014 at 1:04 AM
To: Sachin Bansal <email address hidden>
Cc: Contrail Systems Configuration Team <email address hidden>, Vedamurthy Joshi <email address hidden>
Subject: Creation of a svc_snat n/w with l3 router
Hi Sachin,
Do we have a blue print on our l3 implementation that I can read.
Once I created the l3 router. I see creation of a svc_snat(l3 router uuid) network with a /29 subnet.
I see a port created with name si_(l3 router uuid)-1_left , but I don’t understand what’s SI (service instance?).
The above ports shows that it is attached, but I can’t figure out what device it is attached to. Device owner also comes as None.
-
Rahul