Hello,
I'm not sure how to fix this, but calling 'crm resource restart vm-name' this
morning caused an entire node to get fenced, kicking the stool out from under a
number of VMs.
Looking at VirtualDomain it looks like the system defaults to a 90s timeout,
and if it can't gracefully shutdown
On Wed, 2021-06-30 at 08:40 -0700, Matthew Schumacher wrote:
> Hello,
>
> I'm not sure how to fix this, but calling 'crm resource restart vm-
> name' this morning caused an entire node to get fenced, kicking the
> stool out from under a number of VMs.
>
> Looking at VirtualDomain it looks like
