Hi Itamar,
i assume this is around gluster deployment/split-brains/etc., since we try
to resume and fail
We are progressing on bz.
Looks like quorum configuration playing a role here. I will follow up on
the same bug report.
--Humble
On Mon, Jun 16, 2014 at 7:10 PM, Itamar Heim
Hi,
that has been fixed since 3.3 with auto-resume paused vm's after EIO
Thanks Itamar .
I had a BZ open about this with some traction, but i forgot to keep up
with the requests and it's fallen behind
https://bugzilla.redhat.com/show_bug.cgi?id=1058300
Even manually, they won't resume.
On 06/16/2014 04:20 PM, Humble Devassy Chirammal wrote:
Hi,
that has been fixed since 3.3 with auto-resume paused vm's after EIO
Thanks Itamar .
I had a BZ open about this with some traction, but i forgot to keep up
with the requests and it's fallen behind
On 06/02/2014 01:10 PM, Humble Devassy Chirammal wrote:
Hi Andrew,
Afaict, there should be manual intervention to resume a 'paused vm' in
any storage domain even if VM is marked as HA..
that has been fixed since 3.3 with auto-resume paused vm's after EIO
Also, I failed to understand the
Hi Andrew,
Afaict, there should be manual intervention to resume a 'paused vm' in any
storage domain even if VM is marked as HA..
Also, I failed to understand the setup you have, that said, you mentioned:
resuming a VM from a paused state on top
of NFS share? Even when the VMs are marked as
Hi Humble,
On Mon, Jun 2, 2014 at 8:10 PM, Humble Devassy Chirammal
humble.deva...@gmail.com wrote:
Hi Andrew,
Afaict, there should be manual intervention to resume a 'paused vm' in any
storage domain even if VM is marked as HA..
I had a BZ open about this with some traction, but i forgot to
Hi,
Has anyone had any luck with resuming a VM from a paused state on top
of NFS share? Even when the VMs are marked as HA, if the gluster
storage goes down for a few seconds the VMs go to a paused state and
can never be resumed. They require a hard reset.
I recall when using NFS to not have
7 matches
Mail list logo
