Open Stack

> On 15 Jun 2016, at 22:06, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
> 
> 
>> On 15 Jun 2016, at 21:19, Aaron Rosen <aaronorosen at gmail.com> wrote:
>> 
>> 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
>> 
>> That's what was causing the issue on our end.  All should be okay upstream. Sorry about the confusion. 
>> 
> 
> Great. Thanks for the update, I can now sleep a tad better this night. :) I guess you want to bring this topic up to your distribution folks for them to be aware they are breaking plugins.
> 
> Ihar

btw ironically, the patch in question was proposed for stable/liberty and stable/kilo in upstream but was stopped by stable maintainers for several reasons: 1. it indeed breaks 3party plugins, and we knew about that; 2. it requires controller upgrade before upgrading computes, which is not a requirement for minor (stable) updates (in contrast to major upgrades, like L-to-M).

Discussion at: https://review.openstack.org/#/c/240167/

So kudos to upstream stable process for keeping those breaking changes far from stable branches!

Ihar