Created attachment 1239902 [details] logs Description of problem: Installation failed because vdsm is not stating, and it fails on ssh timeout Version-Release number of selected component (if applicable): rhevm-3.6.10.2-0.2.el6.noarch Red Hat Enterprise Virtualization Hypervisor release 7.3 (20170110.1.el7ev) vdsm-4.17.37-1.el7ev.noarch How reproducible: always Steps to Reproduce: 1. add host to engine 2. 3. Actual results: Expected results: Additional info:
Have you looked why VDSM is not starting?
There is no VDSM logs at all. when trying to systemctl start vdsm -l nothing happens. I saw hooks failures in the installation process, not sure if related (screenshot attached)
Created attachment 1239955 [details] screenshot
I have reproduced the report, investigating.
Just to clarify, from my tests it's not about VDSM. This is report was caused because when we fixed the sat6.2 support we added a new entry "Environment" and autoinstall required the change too.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
QE can reproduce this issue. Test version: rhev-hypervisor7-7.3-20170110.1.iso Test steps: 1. Auto install RHEV-H with rhn_auto parameters. BOOTIF=xxx storage_init=/dev/sda adminpw=xxx rhn_username=xxx rhn_password=xxx rhn_url=xxx rhn_ca_cert=xxx firstboot. Test result: Auto install failed. there is not enough arguments given for <function update at> of <ovirt.node.setup.rhn.rhn_model.RHN> object at xxx.
Created attachment 1240217 [details] /var/log/*.*; /tmp
I will check the logs and see if rhn auto install was working as well in the past.
*** Bug 1413373 has been marked as a duplicate of this bug. ***
Raising priority due to the automation impact
Created attachment 1241156 [details] auto57-all-log
Created attachment 1241157 [details] auto608-all-log
Verify this bug according #c21 & 22