Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-08 Thread Frank Rothenstein
Thanks Thomas, it seems you were right. I followed the instructions to enable hugepages via kernel command line and after reboot vdsmd starts correctly. (I went back to 4.1.9 in between, added the kernel command line and upgraded to 4.2) The docs/release notes should mention it - or did I miss

Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-05 Thread Petr Kotas
Hi Frank, can you please send a vdsm logs? The 4.2 release added the little different deployment from the engine. Now the ansible is also called. Although I am not sure if this is your case. I would go for entirely removing the vdsm and installing it from scratch if it is possible for you. This

[ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-05 Thread Frank Rothenstein
Hi, I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start the host-processes. systemctl start vdsmd fails with following lines in journalctl: Feb 05 14:40:15 glusternode1.bodden-kliniken.net vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network Feb 05 14:40:15