[ovirt-users] Re: System unable to recover after a crash

2019-07-13 Thread Strahil
Hi Carl, I'd recommend you to avoid DNS & DHCP unless you oVirt infra consistes of hundreds of servers. It is far more reliable to use static IPs + /etc/hosts . As you could 'ssh' to the engine, check the logs - there should be a clue why it failed. Most probably it's related to the DNS/IP u

[ovirt-users] Re: System unable to recover after a crash

2019-07-13 Thread carl langlois
Hi Thanks for the info. There have been some progress with the situation. So to make the story as short as possible we are in a process of changing our range of IP addresse to 10.8.X.X to 10.16.X.X for all of the ovirt infra. This implies a new DHCP server, new switchs etc etc. For now we went back

[ovirt-users] Re: System unable to recover after a crash

2019-07-13 Thread Strahil Nikolov
Can you mount the volume manually at another location ?Also, have you done any changes to Gluster ? Please provide "gluster volume info engine" . I have noticed the following in your logs: option 'parallel-readdir' is not recognized Best Regards,Strahil Nikolov В петък, 12 юли 2019 г., 22:30

[ovirt-users] Re: System unable to recover after a crash

2019-07-12 Thread Alex K
On Fri, Jul 12, 2019, 22:30 carl langlois wrote: > Hi , > > I am in state where my system does not recover from a major failure. I > have pinpoint the probleme to be that the hosted engine storage domain is > not able to mount > > I have a glusterfs containing the storage domain. but when it atte