HI,
I re-installed the cluster and got the hosted engine deployed succesfully.
Thank you for your assistance
On Thu, Sep 6, 2018 at 1:54 PM, Sakhi Hadebe wrote:
> Hi Simone,
>
> Yes the ownership of /var/log/ovirt-imageio-daemon is vdsm:kvm, 755.
>
> Below is the version of the ovirt packages
Can you please check if on your host you have /var/log/ovirt-imageio-daemon
and its ownership and permissions (it should be vdsm:kvm,700)?
Can you please report which version of ovirt-imageio-daemon you are using?
We had a bug there but it has been fixed long time ago.
On Wed, Sep 5, 2018 at
Sorry, I mistakenly send the email:
Below is the output of:
[root@glustermount ~]# systemctl status ovirt-imageio-daemon.service -l
● ovirt-imageio-daemon.service - oVirt ImageIO Daemon
Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service;
disabled; vendor preset: disabled)
# systemctl status ovirt-imageio-daemon.service
● ovirt-imageio-daemon.service - oVirt ImageIO Daemon
Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-daemon.service;
disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2018-09-04 16:55:16 SAST;
19h ago
On Wed, Sep 5, 2018 at 11:10 AM Sakhi Hadebe wrote:
> Hi All,
>
> The host deploy logs are showing the below errors:
>
> [root@garlic engine-logs-2018-09-05T08:48:22Z]# cat
>
Hi All,
The host deploy logs are showing the below errors:
[root@garlic engine-logs-2018-09-05T08:48:22Z]# cat
/var/log/ovirt-hosted-engine-setup/engine-logs-2018-09-05T08\:34\:55Z/ovirt-engine/host-deploy/ovirt-host-deploy-20180905103605-garlic.sanren.ac.za-543b536b.log
| grep -i error
On Tue, Sep 4, 2018 at 6:07 PM Sakhi Hadebe wrote:
> Hi Sahina,
>
> I am sorry I can't reproduce the error nor access the logs since I did a
> fresh installed pn nodes. However now I can't even react that far because
> the engine deployment fails to start the host up:
>
>
> [ INFO ] TASK [Wait
Hi Sahina,
I am sorry I can't reproduce the error nor access the logs since I did a
fresh installed pn nodes. However now I can't even react that far because
the engine deployment fails to start the host up:
[ INFO ] TASK [Wait for the host to be up]
[ ERROR ] fatal: [localhost]: FAILED! =>
On Wed, Aug 29, 2018 at 8:39 PM, Sakhi Hadebe wrote:
> Hi,
>
> I am sorry to bother you again.
>
> I am trying to deploy an oVirt engine for oVirtNode-4.2.5.1. I get the
> same error I encountered before:
>
> [ INFO ] TASK [Add glusterfs storage domain]
> [ ERROR ] Error: Fault reason is
Thank you all for your help, I have managed to deploy the engine
successfully. It was a quiet a lesson.
On Wed, Jul 11, 2018 at 11:55 AM, Sakhi Hadebe wrote:
> Hi Sahina,
>
> Yes the glusterd daemon was not running. I have started it and is able to
> add a glusterfs storage domain. Thank you
Hi Sahina,
Yes the glusterd daemon was not running. I have started it and is able to
add a glusterfs storage domain. Thank you so much for your help.
Oops! I allocated 50GiB for this storage domain and it requires 60GiB.
On Wed, Jul 11, 2018 at 11:47 AM, Sahina Bose wrote:
> Is glusterd
Is glusterd running on the server: goku.sanren.**
There's an error
Failed to get volume info: Command execution failed
error: Connection failed. Please check if gluster daemon is operational
Please check the volume status using "gluster volume status engine"
and if all looks ok, attach the mount
On Wed, Jul 11, 2018 at 9:33 AM, Sakhi Hadebe wrote:
> Hi,
>
> Below are the versions of packages installed. Please find the logs
> attached.
> Qemu:
> ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
> libvirt-daemon-driver-qemu-3.9.0-14.el7_5.6.x86_64
>
2018-07-03 14:28 GMT+02:00 Sakhi Hadebe :
> Hi,
>
> We are deploying the hosted engine on oVirt-Node-4.2.3.1 using the command
> "hosted-engine --deploy".
>
Hi, any reason for using command line instead of the cockpit web ui?
>
> After providing answers it runs the ansible script and hit the
vdsm.log does indicate an error connecting to the engine gluster volume.
I should have been more specific - I requested for the engine volume mount
logs from the host, under
/var/log/glusterfs/rhev-data-center-mnt-glusterSD...engine.log
Also, please provide output of "gluster volume status
It looks like a problem accessing the engine gluster volume. Can you
provide the logs from /var/log/gluster/rhev-data*engine.log as well as the
vdsm.log from the host.
On Wed, Jul 4, 2018 at 11:07 AM, Yedidyah Bar David wrote:
> On Tue, Jul 3, 2018 at 3:28 PM, Sakhi Hadebe wrote:
> > Hi,
> >
On Tue, Jul 3, 2018 at 3:28 PM, Sakhi Hadebe wrote:
> Hi,
>
> We are deploying the hosted engine on oVirt-Node-4.2.3.1 using the command
> "hosted-engine --deploy".
>
> After providing answers it runs the ansible script and hit the Error when
> creating glusterfs storage domain. Attached the
17 matches
Mail list logo
