nicira: error occurs when net-gateway-connect with different segmentation-type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VMwareAPI-Team |
New
|
High
|
Unassigned | ||
neutron |
Fix Released
|
Medium
|
Armando Migliaccio | ||
Havana |
Fix Released
|
Medium
|
Armando Migliaccio |
Bug Description
1. create net-gateway and gateway-connection. segmentation-type is vlan and
segmentation_id is 0.
neutron net-gateway-create --device id=c4369a1c-
neutron net-gateway-connect NetworkgatewayName L2-1 --segmentation-type vlan
openstack@
+------
| Field | Value |
+------
| default | False |
| devices | {"interface_name": "eth0", "id": "c4369a1c-
| id | ab76582b-
| name | NetworkgatewayName |
| ports | {"port_id": "2e8d5d83-
| tenant_id | ec2918c3e751415
+------
2. add network to gateway by net-gateway-
openstack@
Request Failed: internal server error while processing your request.
I think Neutron should not return 500.
=====
[Neutron server's log]
It seems conflict of segmentation-id because 0 is already used by vlan.
2014-01-27 11:57:23.805 ERROR NeutronPlugin [-] Unable to create port or set port attachment in NVP.
2014-01-27 11:57:23.819 ERROR neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.819 TRACE neutron.
2014-01-27 11:57:23.852 INFO neutron.wsgi [req-dbf0b9a0-
[net-gatway-connect with vlan which segmentatin-id 0 causes 409]
devstack@
409-{u'
Changed in neutron: | |
assignee: | nobody → Armando Migliaccio (armando-migliaccio) |
Changed in neutron: | |
status: | Incomplete → Confirmed |
tags: | added: havana-backport-potential |
Changed in openstack-vmwareapi-team: | |
importance: | Undecided → High |
Changed in neutron: | |
importance: | Undecided → Medium |
milestone: | none → icehouse-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
If you attempt to do two gateway by net-gateway-connect in sequence you should get a 409 rather than a 500. Is that what you were trying to do? Or did you get a 500 error on the a single gateway by net-gateway-connect using the flat segmentation type?