Open Stack

On 9/1/2016 12:05 PM, Suresh Vinapamula wrote:
> On 8/31/2016 4:17 PM, Dan Smith wrote:
>
>         Thanks Dan for your response. While I do run that before I start my
>         move to liberty, what I see is that it doesn't seem to flavor migrate
>         meta data for the VMs that are spawned after controller upgrade from
>         juno to kilo and before all computes upgraded from juno to kilo. The
>         current work around is to delete those VMs that are spawned after
>         controller upgrade and before all computes upgrade, and then initiate
>         liberty upgrade. Then it works fine.
>
>     I can't think of any reason why that would be, or why it would be a
>     problem. Instances created after the controllers are upgraded should not
>     have old-style flavor info, so they need not be touched by the migration
>     code.
>
>     Maybe filing a bug is in order describing what you see?
>
>     --Dan
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe: openstack-dev-requ... at lists.openstack.org?subject:unsubscribe
>     <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> Also, are you running with the latest kilo patch update? There were
> some bug fixes backported after the release from what I remember.
>
> --
>
> Thanks,
>
> Matt Riedemann
>
> Hi Matt,
>
> Thanks for the response. I am currently using 2015.1.2. From the release notes of 2015.1.4 https://wiki.openstack.org/wiki/ReleaseNotes/2015.1.4, I can't correlate any fixes with this issue. Am I missing something?
>
> thanks
>
> Suresh
>

The things I was looking for look like they are in 2015.1.2 so you 
should be OK there for at least known issues.

-- 

Thanks,

Matt Riedemann