[ovirt-devel] Re: Taking down the engine without setting global maintenance

2019-03-07 Thread Martin Sivak
> When the engine goes down, it can't know if it's part of a > graceful/clean reboot. It can be due to a problem, which is severe > enough to take the machine down and not take it up again, but still > not severe enough to prevent clean shutdown of the engine itself. That and the fact that the

[ovirt-devel] Re: Taking down the engine without setting global maintenance

2019-03-07 Thread Yedidyah Bar David
On Thu, Mar 7, 2019 at 11:41 AM Simone Tiraboschi wrote: > > > > On Thu, Mar 7, 2019 at 10:34 AM Yedidyah Bar David wrote: >> >> On Thu, Mar 7, 2019 at 11:30 AM Martin Sivak wrote: >> > >> > Hi, >> > >> > there is no way to distinguish an engine that is not responsive >> > (software or network

[ovirt-devel] Re: Taking down the engine without setting global maintenance

2019-03-07 Thread Simone Tiraboschi
On Thu, Mar 7, 2019 at 10:34 AM Yedidyah Bar David wrote: > On Thu, Mar 7, 2019 at 11:30 AM Martin Sivak wrote: > > > > Hi, > > > > there is no way to distinguish an engine that is not responsive > > (software or network issue) from a VM that is being powered off. The > > shutdown takes some

[ovirt-devel] Re: Taking down the engine without setting global maintenance

2019-03-07 Thread Yedidyah Bar David
On Thu, Mar 7, 2019 at 11:30 AM Martin Sivak wrote: > > Hi, > > there is no way to distinguish an engine that is not responsive > (software or network issue) from a VM that is being powered off. The > shutdown takes some time during which you just do not know. _I_ do not know, but the user might

[ovirt-devel] Re: Taking down the engine without setting global maintenance

2019-03-07 Thread Martin Sivak
Hi, there is no way to distinguish an engine that is not responsive (software or network issue) from a VM that is being powered off. The shutdown takes some time during which you just do not know. Global maintenance informs the tooling in advance that something like this is going to happen. Who