[ovirt-users] Problem with hosted engine setup - vsdmd does not start

[Willard Dennis]

OK, should not have used the term “vanilla” I guess… I have customized the OS to fit into my environment (not so much with kickstart, mostly via Ansible) and of course have installed Gluster 3.7 and configured volumes for the engine and VM storage. So it’s not like it’s running on a completely stock CentOS 7 install (that would be basically unusable for me…)

Doing a complete reinstall would be many hours of work (already have done that once to reconfigure Gluster) so not really interested in doing that…

I’d love to continue debugging; just frustrated that everything done so far has not worked (read thread for details…) and we cannot get the vdsmd service to run… I do very much appreciate the assistance of all the RHAT folks who have responded to this thread, you are my only hope of getting this stuff running, as I’m not an oVirt expert by far....

-Will

> On Dec 17, 2015, at 1:40 AM, Yedidyah Bar David <didi at redhat.com> wrote:
> 
> On Wed, Dec 16, 2015 at 11:52 PM, Willard Dennis <wdennis at nec-labs.com> wrote:
>> Any thoughts on this issue?? This is holding up my project (oVirt hosted
>> engine install won’t proceed if VDSM service is not running…)  Why am I even
>> having such problems with the VDSM service? It’s on a vanilla CentOS 7
>> install…
> 
> (Only briefly skimming the history of this thread:)
> 
> If all you want is to have it up and running, I'd suggest reinstalling
> the OS and then try again. Quite likely you have there some local
> non-default configurations or something. If it still fails, I'd suggest
> to open a bug, describe exact flow, and attach all relevant logs. When
> you reinstall the OS, keep in mind that things like a custom kickstart
> file etc are also non-default configurations, so if you need them,
> attach them to the bug as well.
> 
> If you are aware of such non-default stuff but do need them, you
> basically have two choices:
> 1. Keep on debugging this til it works. We can try helping, but can't
> guess every change you did to your system. In particular, as Simone
> said before, sudo is configured to work out-of-the-box by default.
> 2. Try a clean vanilla OS install on another system and compare them
> to try and see what difference breaks. This can be done also on a VM
> with nested kvm, if you do not have a spare physical machine.
> 
> Best,
> -- 
> Didi