Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-10-03 Thread Suresh Vinapamula
Hi, I did some investigation last week, why this was happening before I file the bug. Here are my observations and I would like to work on it. Any guidance is appreciated. Upgrade procedure: In my setup I have openstack controller on one node, neutron on another node and rest of the nodes are

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-09-01 Thread Matt Riedemann
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

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-09-01 Thread Suresh Vinapamula
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

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Matt Riedemann
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

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Suresh Vinapamula
Sure, will file a bug with my observations. On Wed, Aug 31, 2016 at 2: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

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Suresh Vinapamula
>> While migrate_flavor_data seem to flavor migrate meta data of the VMs >> that were spawned before upgrade procedure, it doesn't seem to flavor >> migrate for the VMs that were spawned during the upgrade procedure more >> specifically after openstack controller upgrade and before compute >>

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Dan Smith
> 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

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Dan Smith
> While migrate_flavor_data seem to flavor migrate meta data of the VMs > that were spawned before upgrade procedure, it doesn't seem to flavor > migrate for the VMs that were spawned during the upgrade procedure more > specifically after openstack controller upgrade and before compute > upgrade.

[openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

2016-08-31 Thread Suresh Vinapamula
Hi, I am upgrading from Juno to Kilo and from that to Liberty. I understand I need to nova-manage db migrate_flavor_data before upgrading from Kilo to Liberty to let VMs that were spawned while the system was in Juno to flavor migrate to Kilo. Depending on the number of computes, complete