Hi,
On Thu, Feb 7, 2019 at 9:27 AM Sahina Bose wrote:
> +Sachidananda URS to review user request about systemd mount files
>
> On Tue, Feb 5, 2019 at 10:22 PM feral wrote:
> >
> > Using SystemD makes way more sense to me. I was just trying to use
> ovirt-node as it was ... intended? Mainly
+Sachidananda URS to review user request about systemd mount files
On Tue, Feb 5, 2019 at 10:22 PM feral wrote:
>
> Using SystemD makes way more sense to me. I was just trying to use ovirt-node
> as it was ... intended? Mainly because I have no idea how it all works yet,
> so I've been trying
Using SystemD makes way more sense to me. I was just trying to use
ovirt-node as it was ... intended? Mainly because I have no idea how it all
works yet, so I've been trying to do the most stockish deployment possible,
following deployment instructions and not thinking I'm smarter than the
Dear Feral,
>On that note, have you also had issues with gluster not restarting on reboot,
>as well as >all of the HA stuff failing on reboot after power loss? Thus far,
>the only way I've got the >cluster to come back to life, is to manually
>restart glusterd on all nodes, then put the
Fyi, this is just a vanilla install from the ovirt node 4.2 iso. Install 3
nodes, sync up hosts file and exchange SSH keys, and hit the webui for
hyperconverged deployment. The only setting I enter that make it into the
config, are the hostnames.
On Mon, Feb 4, 2019, 8:44 PM Gobinda Das Sure
Sure Greg, I will look into this and get back to you guys.
On Tue, Feb 5, 2019 at 7:22 AM Greg Sheremeta wrote:
> Sahina, Gobinda,
>
> Can you check this thread?
>
> On Mon, Feb 4, 2019 at 6:02 PM feral wrote:
>
>> Glusterd was enabled, just crashes on boot. It's a known issue that was
>>
Sahina, Gobinda,
Can you check this thread?
On Mon, Feb 4, 2019 at 6:02 PM feral wrote:
> Glusterd was enabled, just crashes on boot. It's a known issue that was
> resolved in 3.13, but ovirt-node only has 3.12.
> The VM is at that point, paused. So I manually startup glusterd again and
>
Glusterd was enabled, just crashes on boot. It's a known issue that was
resolved in 3.13, but ovirt-node only has 3.12.
The VM is at that point, paused. So I manually startup glusterd again and
ensure all nodes are online, and then resume the hosted engine. Sometimes
it works, sometimes not.
I
On each host you should check if systemctl status glusterd shows "enabled"
and whatever is the gluster events daemon. (I'm not logged in to look right
now)
I'm not sure which part of gluster-wizard or hosted-engine engine
installation is supposed to do the enabling, but I've seen where incomplete
On that note, have you also had issues with gluster not restarting on
reboot, as well as all of the HA stuff failing on reboot after power loss?
Thus far, the only way I've got the cluster to come back to life, is to
manually restart glusterd on all nodes, then put the cluster back into "not
Yea, I've been able to build a config manually myself, but sure would be
nice if the gdeploy worked (at all), as it takes an hour to deploy every
test, and manually creating the conf, I have to be super conservative about
my sizes, as I'm still not entirely sure what the deploy script actually
Yes, I had that issue with an 4.2.8 installation.
I had to manually edit the "web-UI-generated" config to be anywhere close
to what I wanted.
I'll attach an edited config as an example.
On Mon, Feb 4, 2019 at 2:51 PM feral wrote:
> New install of ovirt-node 4.2 (from iso). Setup each node with
12 matches
Mail list logo
