[openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.
Suresh Vinapamula
suresh.vin at gmail.com
Wed Aug 31 21:36:55 UTC 2016
Sure, will file a bug with my observations.
On Wed, Aug 31, 2016 at 2:17 PM, Dan Smith <dms at danplanet.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160831/9097ec28/attachment.html>
More information about the OpenStack-dev
mailing list