Description of problem: In engine.log we see every couple seconds following error message: 65366:2017-02-21 22:13:34,357 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (DefaultQuartzScheduler10) [2dc75859] null architecture type, replacing with x86_64, %s Version-Release number of selected component (if applicable): How reproducible: Don't know, but Simone mentioned that he saw it already around. Steps to Reproduce: Don't know. Actual results: Error in engine.log Expected results: Don't know. Not having this error? Additional info: I'm not sure to what this error message even relates. As such I'm not sure what the expected result should be nor what the impact currently is.
Which VM is that? It should be right around this log line.... please include a bit more of the log
2017-02-24 14:45:55,958 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [25220ea5] VM 'b0fd2dbe-c62d-477c-8045-5a29941b9259' that is set as hosted-engine was discovered with status 'Up' on VDS '2080b45a-0d86-4012-b56f-550c27a23d6e'(bio2_engine) 2017-02-24 14:45:56,216 INFO [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] (DefaultQuartzScheduler3) [417157e0] Running command: AddUnmanagedVmsCommand internal: true. 2017-02-24 14:45:56,216 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (DefaultQuartzScheduler3) [417157e0] START, FullListVDSCommand(HostName = , FullListVDSCommandParameters:{runAsync='true', hostId='2080b45a-0d86-4012-b56f-550c27a23d6e', vds='Host[,2080b45a-0d86-4012-b56f-550c27a23d6e]', vmIds='[b0fd2dbe-c62d-477c-8045-5a29941b9259]'}), log id: 7563ee6 2017-02-24 14:45:57,187 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVDSCommand] (DefaultQuartzScheduler3) [417157e0] FINISH, FullListVDSCommand, return: [{status=Up, nicModel=rtl8139,pv, emulatedMachine=pc, guestDiskMapping={}, vmId=b0fd2dbe-c62d-477c-8045-5a29941b9259, pid=8650, devices=[Ljava.lang.Object;@52b3bcb2, smp=4, vmType=kvm, displayIp=0, display=vnc, displaySecurePort=-1, memSize=8192, displayPort=5900, cpuType=SandyBridge, spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir, statusTime=4644870000, vmName=HostedEngine, clientIp=, pauseCode=NOERR}], log id: 7563ee6 2017-02-24 14:45:57,188 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (DefaultQuartzScheduler3) [417157e0] null architecture type, replacing with x86_64, %s
ah, ok, i recall some issue in HE import. It's should be harmless though as the import is done only once, but if you see it periodically there is likely some import HE VM problem
It comes every few seconds / minutes. It's possible though there is an issue because our HE storage domain is currently locked, which is a bug that's apparently fixed in 4.1... Could this be?
I noticed this in my environment also - fresh install. The errors when away after I configured my first storage domain (needed for HE storage domain to import successfully) rhvh-4.0-0.20170307.0 rhevm-appliance-20170307.0-1.x86_64.rhevm.ova ovirt-engine-4.0.7.4-0.1.el7ev.noarch
Can this BZ move to MODIFIED, or additional patches are needed?
verified in rhvm-4.2.0-0.6.el7.noarch built new HE environment . added storage, template from glance, created VM from template. Result: no "null architecture type" error in engine.log
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.