Thanks for the updates. From: Aaron Rosen <[email protected]> Reply-To: OpenStack List <[email protected]> Date: Wednesday, June 15, 2016 at 10:19 PM To: OpenStack List <[email protected]> Subject: Re: [openstack-dev] [Neutron] Stable/liberty breakage
Sorry I think I gave Gary some bad information here. After digging into this more, the actually underlying issue that we hit is that the packaged 'distro' version of stable/liberty that was running with the vmware-nsx repo included this patch set which is not in upstream stable/liberty https://github.com/openstack/neutron/commit/7267d75fdd3f90af759d71e9490cd41d41ba6d98<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_neutron_commit_7267d75fdd3f90af759d71e9490cd41d41ba6d98&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=W892wB0u3s_K0vG45Yac48hZEChj_a0By3Wz56bodqo&s=KsyWOnTC6FV2c0x0IBbJo1Dg6D91uhYGNgqO4TMo5_k&e=> That's what was causing the issue on our end. All should be okay upstream. Sorry about the confusion. Aaron On Wed, Jun 15, 2016 at 11:59 AM, Ihar Hrachyshka <[email protected]<mailto:[email protected]>> wrote: > On 15 Jun 2016, at 20:18, Gary Kotton > <[email protected]<mailto:[email protected]>> wrote: > > Hi, > The following patch breaks stable liberty drivers - > https://review.openstack.org/#/c/238745/ > This means that plugins will need to be updated to support this. Would you mind sharing details about the breakage? It was assumed that the patch backported includes the relevant compatibility bits to avoid any breakage. If that’s not the case, we should definitely come up with a way to get existing drivers unbroken again. > What do we do: > • Revert – which could break people using latest stable/liberty > • Have a requirement that Neutron plugins be updated when they use > stable/liberty It may be either revert, or a new patch that would accommodate for your broken driver. It depends on breakage details. So please share those. > This is really bad. Absolutely. The change was not expected to require any changes for 3party drivers. If it happened, that’s our fault, and maybe we should land something, or revert. We should not leave it broken for 3party drivers. > Any suggestions. > Thanks > Gary > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
