OVS to ml2 migration doesn't handle ports with no value for binding:host_id

Bug #1424378 reported by Chen Leibovich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

While working on the upgrade process from Havana to Icehouse we noticed that the ml2 migration doesn't handle ports with no value for binding:host_id.

I first came across this issue when I had issues with DHCP ports which I was able to work around by deleting them and recreating them by restarting the dhcp agent.

The bigger issue came when we moved on to production where we had instances that were created back in Folsom and undergone the Folsom->Grizzly->Havana->Icehouse upgrades.

The network for these instances wasn't restored after the upgrade + there were a lot of nova-compute exceptions when trying to reboot those instances.

Revision history for this message
Chen Leibovich (cleibovich) wrote :

Output of neutron port-show for such port in Havana with OVS plugin:
+-----------------------+-----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-----------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:capabilities | {"port_filter": true} |
| binding:host_id | |
| binding:vif_type | ovs |
| device_id | d3b3b5be-0611-4a4f-86ca-b130d0613abf |
| device_owner | compute:nova |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "f070b025-5927-4633-8942-d3144456adb2", "ip_address": "10.59.72.8"} |
| id | 0def1563-c512-4687-9892-bfef79dfb9f3 |
| mac_address | fa:16:3e:09:62:8c |
| name | |
| network_id | 5d7782dc-9ae9-4c22-bd9d-223935c23d76 |
| security_groups | |
| status | ACTIVE |
| tenant_id | bda89c21cefe4f03a29f3cd2c1b85c57 |
+-----------------------+-----------------------------------------------------------------------------------+

Output of neutron port-show for the same port after the upgrade and migration to ml2:

+-----------------------+-----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-----------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| device_id | d3b3b5be-0611-4a4f-86ca-b130d0613abf |
| device_owner | compute:nova |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "f070b025-5927-4633-8942-d3144456adb2", "ip_address": "10.59.72.8"} |
| id | 0def1563-c512-4687-9892-bfef79dfb9f3 |
| mac_address | fa:16:3e:09:62:8c |
| name | |
| network_id | 5d7782dc-9ae9-4c22-bd9d-223935c23d76 |
| security_groups | |
| status | ACTIVE |
| tenant_id | bda89c21cefe4f03a29f3cd2c1b85c57 |
+-----------------------+-----------------------------------------------------------------------------------+

All of the binding:*** attributes are gone.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 365 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 :

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

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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