What I'm saying is, if you configure allow_resize_to_same_host, it means that it will add the same host to the destination options.
If you have compute1, compute2, and compute3 and the instance resides on compute1, here is how it looks:
With allow_resize_to_same_host=False, compute2 and compute3 are the possible destinations.
With allow_resize_to_same_host=True, compute1, compute2, and compute3 are the possible destinations.
You are not configuring same host resize. You are configuring that same host is legal. By default, it is not.
But I guess you are asserting that the meaning of the config setting is not expected by a user.
I'm going to mark this as Invalid since it's not a bug given the meaning of the configuration setting. Please post on the mailing list if you'd like to start a discussion around the config setting.
What I'm saying is, if you configure allow_resize_ to_same_ host, it means that it will add the same host to the destination options.
If you have compute1, compute2, and compute3 and the instance resides on compute1, here is how it looks:
With allow_resize_ to_same_ host=False, compute2 and compute3 are the possible destinations.
With allow_resize_ to_same_ host=True, compute1, compute2, and compute3 are the possible destinations.
You are not configuring same host resize. You are configuring that same host is legal. By default, it is not.
But I guess you are asserting that the meaning of the config setting is not expected by a user.
I'm going to mark this as Invalid since it's not a bug given the meaning of the configuration setting. Please post on the mailing list if you'd like to start a discussion around the config setting.