Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1425863

Summary:	[TEXT] null architecture type, replacing with x86_64, %s
Product:	[oVirt] ovirt-engine	Reporter:	Trefex <trefex>
Component:	Backend.Core	Assignee:	Denis Chaplygin <dchaplyg>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Polina <pagranat>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.0.6.3	CC:	bugs, dchaplyg, dfediuck, michal.skrivanek, mwest, trefex
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ rule-engine: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+
Target Release:	4.2.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-12 10:12:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Trefex 2017-02-22 15:47:42 UTC

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.

Comment 1 Michal Skrivanek 2017-02-23 05:56:31 UTC

Which VM is that? It should be right around this log line....
please include a bit more of the log

Comment 2 Trefex 2017-02-24 13:46:40 UTC

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

Comment 3 Michal Skrivanek 2017-02-24 13:49:18 UTC

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

Comment 4 Trefex 2017-02-24 16:26:26 UTC

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?

Comment 5 Marcus West 2017-04-21 03:28:29 UTC

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

Comment 6 Yaniv Kaul 2017-10-15 09:18:57 UTC

Can this BZ move to MODIFIED, or additional patches are needed?

Comment 8 Polina 2018-01-23 12:56:08 UTC

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

Comment 9 Sandro Bonazzola 2018-02-12 10:12:03 UTC

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.