neutron

Neutron migration to Juno breaks router functionality if ports in tenant other than router

Bug #1484290 reported by Kevin Stevens on 2015-08-12

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	neutron	Expired	Undecided	Unassigned

Bug Description

During recent upgrade from Icehouse to Juno, we lost all interfaces on the backside of the router. Plugging the appropriate values into the neutron.routerports table corrected the issue.

From /usr/local/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/versions/544673ac99ab_add_router_port_table.py , I find the SQL statement to populate the routerports table:
...
SQL_STATEMENT = (
    "insert into routerports "
    "select "
    "p.device_id as router_id, p.id as port_id, p.device_owner as port_type "
    "from ports p join routers r on (p.device_id=r.id) "
    "where "
    "(r.tenant_id=p.tenant_id AND p.device_owner='network:router_interface') "
    "OR (p.tenant_id='' AND p.device_owner='network:router_gateway')"
)
...

Running the same statement reflects the status of the routerports table when the issue was discovered:

MariaDB [neutron]> select p.device_id as router_id, p.id as port_id, p.device_owner as port_type from ports p join routers r on (p.device_id=r.id) where (r.tenant_id=p.tenant_id AND p.device_owner='network:router_interface') OR (p.tenant_id='' AND p.device_owner='network:router_gateway');
+--------------------------------------+--------------------------------------+--------------------------+
| router_id | port_id | port_type |
+--------------------------------------+--------------------------------------+--------------------------+
| 8c5ca5e2-5dc1-4586-8bbe-601a394029fb | 7b280662-37eb-435e-bc20-37b9b824c0b1 | network:router_gateway |
| 8c5ca5e2-5dc1-4586-8bbe-601a394029fb | 8db9bfd3-bd4a-4863-92ef-9c2dbdcbbc0f | network:router_interface |
+--------------------------------------+--------------------------------------+--------------------------+
2 rows in set (0.00 sec)

Removing tenant_id from the WHERE clause seems to be what should have happened. Not sure why we care what the tenant_id is:

MariaDB [neutron]>

Tags:

lvmxh (shaohef) on 2015-08-17

Changed in neutron:
assignee:	nobody → lvmxh (shaohef)

Ann Taraday (akamyshnikova) on 2015-09-08

tags:

added: db

Tom Fifield (fifieldt) on 2015-09-08

tags:

added: ops

Revision history for this message

Tom Fifield (fifieldt) wrote on 2015-09-14:

This bug featured in the Palo Alto Ops meetup in August 2015

lvmxh (shaohef) on 2015-12-03

Changed in neutron:
assignee:	lvmxh (shaohef) → nobody

Revision history for this message

Toni Ylenius (toni-ylenius) wrote on 2016-03-17:

We also bumbed in to the issue after an upgrade. We had a internal gateway router that lost 50 ports in the upgrade. Just wanted to let you know that bug might be still relevant. However, in my opinion this can also be considered as known issue only.

Revision history for this message

Armando Migliaccio (armando-migliaccio) wrote on 2017-02-01:

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-04-02:

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.