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 co
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 con
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 j
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
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 spawned after control
>> 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
>> upgra
> 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
> 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. A
