Currently,  does not skip error instances from evacuating.
However, it does make it back to error after evacuating the instance.
If your requirement does not satisfied with that, then the next option will be
create a option for not to evacuate error VMs first place.
Because, solution proposed in , there will be small chance that
the VM will be
active for a small time and it will cause critical problems in
1ACT/n SBY or any HA model.
On Tue, Jul 11, 2017 at 2:51 AM, Rikimaru Honjo
> Hello all,
> Current Masakari also rescues ERROR instances when host failure happen.
> Those instances will be changed to ACTIVE after rescued.
> But I think that some users don't want to rescue ERROR instances.
> For example, if user is running 1ACT/n SBY application on instances,
> launching ERROR instances will cause unexpected effect.
> So I want to add a configurable option.
> ERROR instances won't be rescued if the option is set.
> Please talk your opinion about this issue.
> I talked about this issue in IRC meeting.
> But time was up at that time.
> This is Evacuate API's behavior.
> There is a possibility that following patch resolve this issue,
> but that will take time.
> Best regards,
> Rikmaru Honjo
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)