OpenStack Compute (nova)

Migration may migrate the instance to the same host, which is meaningless!

Bug #1160268 reported by QiangGuan on 2013-03-26

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	Undecided	QiangGuan	OpenStack Compute (nova) 2013.2 "havana"

Bug Description

For resizing process, if flavor_id is None, it's considered a migration.
Generally speaking, Migration to the same host is meaningless, which is allowed in the current code logic.

OpenStack Infra (hudson-openstack) on 2013-03-26

Changed in nova:
assignee:	nobody → QiangGuan (hzguanqiang)
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-04-01: Fix merged to nova (master)

Reviewed: https://review.openstack.org/25373
Committed: http://github.com/openstack/nova/commit/0fe9beb7c0ae763c9d5bfd8598ec7e79b2fbf42c
Submitter: Jenkins
Branch: master

commit 0fe9beb7c0ae763c9d5bfd8598ec7e79b2fbf42c
Author: Guan Qiang <email address hidden>
Date: Tue Mar 26 17:47:11 2013 +0800

Fix migrating instance to the same host.

In current code logic, Migration to the same host is allowed which is
meaningless.

    In the patch, a Conf flag 'allow_migrate_to_same_host' is added and set to
    false as default. When 'allow_migrate_to_same_host' is false, the current
    instance host will be added into filter property 'ignore_hosts' to avoid
    migrating instance to the same host.

Fixes: bug #1160268

Change-Id: I5ac0391cf468310a89fb6d8a8f5120c5654cb4ff