Logged a bug [1] and submitted a fix [2]. Review away!
[1] https://bugs.launchpad.net/nova/+bug/1427944
[2] https://review.openstack.org/#/c/161069/
- Joe
> On Mar 3, 2015, at 4:42 PM, Jay Pipes wrote:
>
> On 03/03/2015 06:55 AM, Joe Cropper wrote:
>>> On Mar 3, 2015, at 8:34 AM, Vishvananda
On 03/03/2015 06:55 AM, Joe Cropper wrote:
On Mar 3, 2015, at 8:34 AM, Vishvananda Ishaya
wrote:
I’m pretty sure it has always done this: leave the host set on the
final scheduling attempt. I agree that this could be cleared which
would free up room for future scheduling attempts.
Thanks Vish
> On Mar 3, 2015, at 8:34 AM, Vishvananda Ishaya wrote:
>
> I’m pretty sure it has always done this: leave the host set on the final
> scheduling attempt. I agree that this could be cleared which would free up
> room for future scheduling attempts.
>
Thanks Vish for the comment. Do we know
I’m pretty sure it has always done this: leave the host set on the final
scheduling attempt. I agree that this could be cleared which would free up room
for future scheduling attempts.
Vish
On Mar 3, 2015, at 12:15 AM, Joe Cropper wrote:
> Hi Folks,
>
> I was wondering if anyone can comment
Hi Folks,
I was wondering if anyone can comment on the intended behavior of how
instance.host is supported to be set during reschedule operations. For
example, take this scenario:
1. Assume an environment with a single host… call it host-1
2. Deploy a VM, but force an exception in the spawn pa
