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

Matt Riedemann mriedemos at gmail.com
Thu Dec 14 15:15:18 UTC 2017

I'm not sure how many other projects still have an active stable/newton 
branch, but I know nova is one of them.

At this point, these are I think the things that need to get done to end 
of life the newton branch for nova:

1. We have a set of existing stable/newton backports that need to get 


3 of those are related to a CVE errata, and the other is an API 
regression introduced in Newton (trivial low-risk fix).

Those can't merge until the corresponding Ocata backports are merged 
first. I'll start pinging people for reviews on the Ocata backports.

2. Fix and backport https://bugs.launchpad.net/nova/+bug/1738094

This came up just yesterday but it's an upgrade impact introduced in 
Newton so while we have the branch available I think we should get a fix 
there before EOL. There are going to be at least two fixes for this bug:

a) Don't store all of the instance group (members and policies) in the 
request_specs table. I think this is a correct fix but I also think 
because of how instance groups and request spec code tends to surprise 
you with funny bugs in funny ways, it's high risk to backport this to 
newton. Dan has a patch started though: 

b) Alter the request_specs.spec column from TEXT to MEDIUMTEXT, just 
like the build_requests.instance column was increased for similar 
reasons (instance.user_data alone is a MEDIUMTEXT column). This is a 
straight forward schema migration and I think is low risk to backport 
all the way to Newton.




More information about the OpenStack-dev mailing list