Bug 1010578

Summary: host unresponsive during all-in-one installation
Product: [Retired] oVirt Reporter: Rob Oakes <rob.oakes>
Component: ovirt-engine-installerAssignee: Ofer Schreiber <oschreib>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3CC: acathrow, alonbl, cybertimber2000, dougsland, iheim, juan.hernandez, mtrudel, rob.oakes, sbonazzo, sluskyb, yeylon
Target Milestone: ---Flags: alonbl: needinfo? (rob.oakes)
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-07 09:22:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log file from failed installation
none
Install logs
none
VDSM error while installing oVirt none

Description Rob Oakes 2013-09-21 17:49:33 UTC
Description of problem: If the all-in-one installer is run without having the ovirt-engine-websocket-proxy package installed, it causes the installation to fail.


Version-Release number of selected component (if applicable): 3.3.3


How reproducible: Begin a clean all-in-one installation according to the instructions athttp://community.redhat.com/up-and-running-with-ovirt-3-3/. Without also installing ovirt-engine-websocket-proxy, the installation will fail.

Actual results: The installation fails with the error that VDSM is in a failed state. Error in the log: no ovirt-engine-websocket-proxy, no such file or directory.


Expected results: The absence of the websocket proxy should not cause the all-in-one installer to fail. The installer should be able to detect it is absent and omit the proxy routines in the VDSM setup and activation.

Comment 1 Rob Oakes 2013-09-21 17:55:39 UTC
Created attachment 800953 [details]
Log file from failed installation

Comment 2 Cybertimber2011 2013-09-22 19:19:50 UTC
I was working with Rob in IRC and I think I was able to reproduce this. The engine-setup completes, but VDSM fails in the allinone install. 

         --== END OF SUMMARY ==--

[ INFO  ] Starting engine service
[ INFO  ] Restarting httpd
[ INFO  ] Waiting for VDSM host to become operational. This may take several minutes...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ ERROR ] The VDSM host was found in a failed state. Please check engine and bootstrap installation logs.
[WARNING] Local storage domain not added because the VDSM host was not up. Please add it manually.
[ INFO  ] Restarting nfs services
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20130922151400-setup.conf'
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20130922145650.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of setup completed successfully

Install logs to be attached. I'm going to try installing ovirt-engine-websocket-proxy, engine-cleanup, and then reinstall.

Comment 3 Cybertimber2011 2013-09-22 19:22:35 UTC
Created attachment 801322 [details]
Install logs

Install logs w/o ovirt-engine-websocket-proxy being installed. engine-setup succeeds, but VDSM fails.

Comment 4 Itamar Heim 2013-09-24 21:34:13 UTC
similar to http://gerrit.ovirt.org/#/c/19344/?

Comment 5 Alon Bar-Lev 2013-09-24 21:45:08 UTC
The error that is mentioned is not causing setup to stop. The websocket proxy is not the reason why vdsm fails to install.

Please attach:
/var/log/ovirt-engine/engine.log
/var/log/ovirt-engine/host-deploy/*.log

Comment 6 Sandro Bonazzola 2013-11-07 09:22:52 UTC
Closing because we don't have enough data for fixing the issue.
Please reopen if you're able to reproduce this with oVirt 3.3.0.1 or 3.3.1 now in beta.

Comment 7 mtrudel 2014-01-09 19:33:39 UTC
Hi, 
I juste had the same problem :

[ ERROR ] Timed out while waiting for host to start. Please check the logs.
[WARNING] Local storage domain not added because the VDSM host was not up. Please add it manually.
[ INFO  ] Restarting nfs services
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140109141733-setup.conf'
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140109133830.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ INFO  ] Execution of setup completed successfully

Comment 8 mtrudel 2014-01-09 21:10:43 UTC
Created attachment 847837 [details]
VDSM error while installing oVirt

Comment 7