Hi Kevin, This generally happens when nova does not find enough system resources to resize to the new node. Please check the nova-compute logs and let me know. Thanks. On Oct 29, 2015 9:36 PM, "kevin parrikar" <kevin.parker092 at gmail.com> wrote: > Hello All, > I have single compute node in AZ1(different server vendor) > and two compute nodes in AZ2 ,when i try to resize instance in AZ1 it is > getting restarted in AZ2 with new flavor size which i don't want to happen > hence i set "*allow_resize_to_same_host=True*" and " > *allow_migrate_to_same_host=True*"" on computenode1 which is in AZ1.Now > resize is not happening after showing Success: Scheduled resize of > instance "instance2".Scheduler.log shows " Host filter ignoring hosts: > computenode1" any idea how to make resize to work without restarting in > another AZ. > > resize works fine on AZ with 2 compute nodes but not working > > Thanks and Regards, > Kevin > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20151030/f6308bd0/attachment.html>