Created attachment 640675 [details]
reboot_time_node1

Description of problem:

At present, on adding a New Server, the bootstrapping will take place and the server will be rebooted after the required packages are installed/updated. But though the server is back online within 1-2 minutes, for the UI it takes about 300 sec (5 min) for the Host status to be set to "UP" state. Looks like this is the default wait time set in the script.

----
2012-11-08 04:08:23,291 INFO  [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-48) [4f3edad6] Waiting 300 seconds, for server to finish reboot process.
----

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

rhsc-2.0.techpreview2-0.63.20121019gitffbe992.root.el6ev


How reproducible: Always


Steps to Reproduce:

1. Add a new server 
2. After successful bootstrapping, the server will be rebooted and the Host "Status" will be changed to 'reboot'
3. Now, check the time taken for the Host "Status" to reach the "UP" state. You can confirm the same in the "Events" section as well.

--------
2012-Nov-08, 04:22:44 Detected new Host RHS-node2. Host state was set to Up.
	
2012-Nov-08, 04:17:42 Host RHS-node2 installed
	
2012-Nov-08, 04:17:42 Installing Host RHS-node2. Step: Reboot; Details: Rebooting machine.
--------


Actual results: Currently it waits for 300 seconds (5 minutes) for the server to finish reboot process and change the Host status in UI to UP state even though the server is back online within 1-2 minutes. Why the UI takes 5 min for the status change if the bootstrapping is successfully completed before that??



Expected results:

Why don't we mark the status of the Host as UP as soon the server is back online after reboot and reaches a stable state?


Additional info:

This is what seen in the logs during that time:

----------------------------
2012-11-08 04:08:23,231 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-236) Installation of 10.70.36.53. Received message: <BSTRAP component='VDS Configuration' status='OK'/>. FYI. (Stage: Running second installation script on Host)
2012-11-08 04:08:23,239 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-236) Installation of 10.70.36.53. Received message: <BSTRAP component='RHEV_INSTALL' status='OK'/>. Stage completed. (Stage: Running second installation script on Host)
2012-11-08 04:08:23,248 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (NioProcessor-236) Installation of 10.70.36.53. Received message: <BSTRAP component='Reboot' status='OK' message='Rebooting machine' />. FYI. (Stage: Host installation complete)
2012-11-08 04:08:23,268 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (pool-4-thread-49) [4f3edad6] Script ended, result is {1}
2012-11-08 04:08:23,269 INFO  [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-49) [4f3edad6] After Installation pool-4-thread-49
2012-11-08 04:08:23,274 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-49) [4f3edad6] START, SetVdsStatusVDSCommand(HostName = RHS-node1, HostId = a17bfb18-292b-11e2-adf2-0025907c2e9e, status=Reboot, nonOperationalReason=NONE), log id: 3
f1bf517
2012-11-08 04:08:23,291 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-49) [4f3edad6] FINISH, SetVdsStatusVDSCommand, log id: 3f1bf517
2012-11-08 04:08:23,291 INFO  [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-4-thread-48) [4f3edad6] Waiting 300 seconds, for server to finish reboot process.
2012-11-08 04:10:00,001 INFO  [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-82) Autorecovering hosts is disabled, skipping
2012-11-08 04:10:00,001 INFO  [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-82) Autorecovering storage domains is disabled, skipping
2012-11-08 04:13:23,293 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-48) [4f3edad6] START, SetVdsStatusVDSCommand(HostName = RHS-node1, HostId = a17bfb18-292b-11e2-adf2-0025907c2e9e, status=NonResponsive, nonOperationalReason=NONE), log id: 4500e662
2012-11-08 04:13:23,312 INFO  [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-4-thread-48) [4f3edad6] FINISH, SetVdsStatusVDSCommand, log id: 4500e662
2012-11-08 04:13:25,969 INFO  [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (QuartzScheduler_Worker-92) [c36dcf3] Running command: InitVdsOnUpCommand internal: true.
----------------------------

engine/server logs and screenshots of "Events" are attached! Let me know if you need any additional information.