Hide Forgot
Description of problem: I've installed a host, and didn't do much with it, but I see it's continuously asked: 2016-03-24 08:55:21,436 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-93) [c51fd9c] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Mess age: Status of host lago_basic_suite_master_host1 was set to Up. ... 2016-03-24 09:38:22,659 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (ForkJoinPool-1-worker-1) [4caedb42] START, GetHardwareInfoVDSCommand(HostName = lago_basic_suite_master_host1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='4e27eade-5df5-4eab-8b43-ab9b6227210e', vds='Host[lago_basic_suite_master_host1,4e27eade-5df5-4eab-8b43-ab9b6227210e]'}), log id: 16795e53 2016-03-24 09:38:23,663 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (ForkJoinPool-1-worker-1) [4caedb42] FINISH, GetHardwareInfoVDSCommand, log id: 16795e53 2016-03-24 09:38:23,673 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (ForkJoinPool-1-worker-1) [47558107] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 4e27eade-5df5-4eab-8b43-ab9b6227210e Type: VDS 2016-03-24 09:38:23,675 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (ForkJoinPool-1-worker-1) [5b4c0d3c] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 4e27eade-5df5-4eab-8b43-ab9b6227210e Type: VDS 2016-03-24 09:38:37,665 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (ForkJoinPool-1-worker-1) [5b4c0d3c] START, GetHardwareInfoVDSCommand(HostName = lago_basic_suite_master_host1, VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', hostId='4e27eade-5df5-4eab-8b43-ab9b6227210e', vds='Host[lago_basic_suite_master_host1,4e27eade-5df5-4eab-8b43-ab9b6227210e]'}), log id: 2f053b3c 2016-03-24 09:38:37,668 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (ForkJoinPool-1-worker-1) [5b4c0d3c] FINISH, GetHardwareInfoVDSCommand, log id: 2f053b3c 2016-03-24 09:38:37,681 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (ForkJoinPool-1-worker-1) [6fee838b] Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 4e27eade-5df5-4eab-8b43-ab9b6227210e Type: VDS 2016-03-24 09:38:37,684 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (ForkJoinPool-1-worker-1) [182f10d4] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 4e27eade-5df5-4eab-8b43-ab9b6227210e Type: VDS Version-Release number of selected component (if applicable): ovirt-engine-4.0.0-0.0.master.20160323171719.git71fa3c8.el7.centos.noarch How reproducible: Did it via Lago, not sure how - can try later. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
GetHardwareInfoVDSCommand is more of an infra verb. Bronheim, can you tell why is it called so often? I do not think that it is related to https://gerrit.ovirt.org/#/c/54644/
Yes this is infra. I see that nothing changed regarding who uses this call - only in VdsManager::refreshCaps triggers it every 15sec indeed. Do you want to change this behavior?
(In reply to Yaniv Bronhaim from comment #2) > Yes this is infra. I see that nothing changed regarding who uses this call - > only in VdsManager::refreshCaps triggers it every 15sec indeed. Do you want > to change this behavior? Any reason to call it every 15 seconds? It floods the logs, and I see no value in it.
Please provide the entire engine.log. The GetHardwareInfoVDSCommand verb is called only as part of refreshCapibilities which has no periodic scheduled job - it is supposed to be called only on certain cases.
It is under the interval part but not always the refresh calls to getCaps which calls to getHardwareInfo, there are some statuses that refresh doesn't check the capabilities such as UP and Maintenance. Logs both from engine and vdsm can assist to understand
Yaniv, could you please logs so we can investigate the issue?
Will re-open if I see it again. Failed to even install hosts on master for way too long :(