[openstack-dev] [nova][stable] What nova needs to get to newton end of life

Matt Riedemann mriedemos at gmail.com
Wed Dec 20 18:27:21 UTC 2017

On 12/19/2017 8:16 PM, Matt Riedemann wrote:
> A quick update here.
> There are no outstanding newton backports proposed. I put up the final 
> release request earlier today.
> However, tonight mnaser reported a bug which impacts Pike+ because of a 
> regression introduced in an online data migration from Newton:
> https://bugs.launchpad.net/nova/+bug/1739318
> I have two patches up for this bug so far. One fixes the actual 
> migration, which would help anyone that hasn't run it yet (people 
> upgrading from mitaka or older). The other works around the bug for 
> anyone that has run the migration and is now hitting the side effect in 
> Pike or Queens.
> At this point, I'm not sure if we should hold newton up for the first 
> fix. It's super simple though, and is low risk to backport.
> On the other hand, we have the workaround which we can also backport to 
> stable/pike.
> Anyway, it's late and I wanted to bring these up so people can ponder.

I have backports proposed for the fix with the online data migration 
regression introduced in Newton:


I've also updated the final newton release patch to depend on that fix 
merging in stable/newton.




More information about the OpenStack-dev mailing list