[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Hi Rob, Can you check the gluster's volume ? gluster volume status engine gluster volume heal engine info summary Still, this is strange that the firewall is having such differences. Fastest way to sync that node to the settings from the other is to: 1. Backup /etc/firewalld 2. Remove

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Is this the issue ? on the deployment host the firewall is active but only on eno2, eno1 appears to have decided to be unmanaged … also the deployment host has 17 rules active the other two have 7 each… ZoneInterfaces IP Range Public default eno2* Unmanaged

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

OK so, I enabled the firewall service as recommended but it was already enabled. I scrubbed the whole setup again with ovirt-hosted-engine-cleanup vdsm-tool configure --force systemctl restart libvirtd systemctl restart vdsm I restarted all hosts again. I went to the setup Gluster & Engine

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

You need to set it also permanent via '--permanent', otherwise after a reload - it's gone. Best Regards, Strahil NikolovOn Nov 25, 2019 19:51, Rob wrote: > > [root@ovirt1 ~]# firewall-cmd --add-service=cockpit > Warning: ALREADY_ENABLED: 'cockpit' already in 'public' > success > [root@ovirt1

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

[root@ovirt1 ~]# firewall-cmd --add-service=cockpit Warning: ALREADY_ENABLED: 'cockpit' already in 'public' success [root@ovirt1 ~]# > On 25 Nov 2019, at 17:16, Parth Dhanjal wrote: > > Rather than disabling firewalld, > You can add the ports and restart the firewalld service > > #

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Rather than disabling firewalld, You can add the ports and restart the firewalld service # firewall-cmd --add-service=cockpit # firewall-cmd --add-service=cockpit --permanent On Mon, Nov 25, 2019 at 10:43 PM Amit Bawer wrote: > firewalld is running? > > systemctl disable --now firewalld > >

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

firewalld is running? systemctl disable --now firewalld On Monday, November 25, 2019, Rob wrote: > It can’t be DNS, since the engine runs on a separate network anyway ie > front end, so why can’t it reach the Volume I wonder > > > On 25 Nov 2019, at 12:55, Gobinda Das wrote: > > There could

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

It can’t be DNS, since the engine runs on a separate network anyway ie front end, so why can’t it reach the Volume I wonder > On 25 Nov 2019, at 12:55, Gobinda Das wrote: > > There could be two reason > 1- Your gluster service may not be running. > 2- In Storage Connection there mentioned

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Admin Console: https://10.10.45.11:9090/ or https://192.168.100.38:9090/ [root@ovirt1 ~]# gluster volume status Status of volume: data Gluster process TCP Port RDMA Port Online Pid -- Brick

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

There could be two reason 1- Your gluster service may not be running. 2- In Storage Connection there mentioned may not exists can you please paste the output of "gluster volume status" ? On Mon, Nov 25, 2019 at 5:03 PM Rob wrote: > [ INFO ] skipping: [localhost] > [ INFO ] TASK

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

[ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed":

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

it's plausible that systemctl restart supervdsm is required as well On Mon, Nov 25, 2019 at 12:17 PM Parth Dhanjal wrote: > As such there are no errors in the vdsm log. > Maybe you can try these steps again > > *ovirt-hosted-engine-cleanup* > *vdsm-tool configure --force* > *systemctl restart

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

As such there are no errors in the vdsm log. Maybe you can try these steps again *ovirt-hosted-engine-cleanup* *vdsm-tool configure --force* *systemctl restart libvirtd* *systemctl restart vdsm* And continue with the hosted engine deployment, in case the hosted engine deployment fails you can

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Can you attach the /var/log/vdsm/vdsm.log here? On Mon, Nov 25, 2019 at 2:47 PM Rob wrote: > Yes, > > I’ll restart all Nodes after wiping the failed setup of Hosted engine > using. > > * ovirt-hosted-engine-cleanup* > *vdsm-tool configure --force* > *systemctl restart libvirtd* > *systemctl

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

hmm, I’’l try again, that failed last time. > On 25 Nov 2019, at 09:08, Parth Dhanjal wrote: > > Hey! > > For > Storage Connection you can add - :/engine > And for > Mount Options - backup-volfile-servers=: > > > On Mon, Nov 25, 2019 at 2:31 PM >

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Yes, I’ll restart all Nodes after wiping the failed setup of Hosted engine using. ovirt-hosted-engine-cleanup vdsm-tool configure --force systemctl restart libvirtd systemctl restart vdsm although last time I did systemctl restart vdsm VDSM did not restart maybe that is OK as Hosted Engine

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Can you please share the error in case it fails again? On Mon, Nov 25, 2019 at 2:42 PM Rob wrote: > hmm, I’’l try again, that failed last time. > > > On 25 Nov 2019, at 09:08, Parth Dhanjal wrote: > > Hey! > > For > Storage Connection you can add - :/engine > And for > Mount Options -

[ovirt-users] Re: Engine deployment last step.... Can anyone help ?

Hey! For Storage Connection you can add - :/engine And for Mount Options - backup-volfile-servers=: On Mon, Nov 25, 2019 at 2:31 PM wrote: > So... > > I have got to the last step > > 3 Machines with Gluster Storage configured however at the last screen > > Deploying the Engine to Gluster