Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1424378
Title:
OVS to ml2 migration doesn't handle ports with no value for
binding:host_id
Status in OpenStack Neutron (virtual network service):
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1424378/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
