Hide Forgot
Created attachment 1191836 [details] All logs in RHVH Description of problem: Sometimes, "Upgrade" is gray in Engine side all the time even wait too long, such as more than 2 hours. "Upgrade" should be available in Engine side in short time. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20160817.0.x86_64 imgbased-0.8.4-1.el7ev.noarch redhat-release-virtualization-host-4.0-2.el7.x86_64 redhat-virtualization-host-image-update-placeholder-4.0-2.el7.noarch Red Hat Virtualization Manager Version: 4.0.2.6-0.1.el7ev How reproducible: 40% Tested 5 times, reproduced 2 times Steps to Reproduce: 1. Install RHVH rhvh-4.0-0.20160803.0.x86_64 2. Login RHVH and setup local repos 3. Add RHVH to Engine 4. Wait for more than 2 hours, check the "Upgrade" in Engine side Actual results: After step2, check update is available in RHVH side with "# yum update" After step4, upgrade is still not available in Engine side, "Upgrade" is gray and there is no update icon. Expected results: After step4, upgrade should be available in a short time (maybe in 10 minutes is ok. Sometimes update was available in 5 minutes in my test). The wait time should be set a default time and consistent, and the time can be set and valid. Additional info: 1. Setup update time in Engine is invalid sometimes: # engine-config -s HostPackagesUpdateTimeInHours=1/12 2. Also encountered this issue once in the before build, so this is not regression bug
Created attachment 1191837 [details] log in Engine
> Additional info: > 1. Setup update time in Engine is invalid sometimes: > # engine-config -s HostPackagesUpdateTimeInHours=1/12 '1/12' is not a valid value for HostPackagesUpdateTimeInHours, if you do that you will see following error during engine startup: 2016-08-19 07:26:06,385 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (ServerService Thread Pool -- 42) [] Error parsing option 'HostPackagesUpdateTimeInHours' value: For input string: "1/12" This means that default value (24 hours) will be used instead!!! If you display help for the option using: engine-config -l | grep HostPackagesUpdateTimeInHours you will get following info: HostPackagesUpdateTimeInHours: Refresh rate (in hours) for available host updates check. (Value Type: String) So it's expected users will provide number of hours. But there's a hidden functionality for testing, you can provide the refresh rate also minutes using floating numbers, in your case setting the refresh rate to 5 minutes can be achieved by: engine-config -s HostPackagesUpdateTimeInHours=0.08
And one more thing, the 1st 'check for upgrade' execution is scheduled randomly between 1 minute to 1 hour after engine startup. All following executions are scheduled by HostPackagesUpdateTimeInHours interval.
Thanks for Martin's explanation. 1. I tested scenarios in comment 2 and comment 3, are all passed. 2. But for the hidden functionality for testing: # engine-config -s HostPackagesUpdateTimeInHours=0.08 We must restart ovirt-engine service to make it valid. So this is not a bug, I will close it.