Bug 4594

Summary:	[AUtobuilder] dmesg sanity test failed because of network issue
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Bogdan Marinescu <bogdan.a.marinescu>
Component:	core	Assignee:	Stefan Stanacar <sstncr>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher, ross.burton, sgw
Version:	1.5
Target Milestone:	1.5
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Bogdan Marinescu 2013-06-03 07:27:05 UTC

http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-systemd/builds/33/steps/Running%20Sanity%20Tests/logs/stdio

 spawn ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.7.2 sh /tmp/test/dmesg.sh
| Warning: Permanently added '192.168.7.2' (RSA) to the list of known hosts.
| /bin/dmesg
| QEMU: There is some error log in dmesg:
| QEMU: ##### Error Log ######
| >systemd-udevd[83]: error changing net interface name eth0 to enp0s3: Device or resource busy
| QEMU: #####    End     ######
| 	Test_Info: Dmesg Test FAIL, Pls. check above error log

Comment 1 Saul Wold 2013-06-04 16:50:12 UTC

Systemd related?

Comment 2 Ross Burton 2013-06-11 09:46:51 UTC

Can we whitelist error messages?  Alternatively, tell systemd not to rename interfaces in qemu.

The error is because systemd is renaming the interface to something "more useful" (ha!) but as we're doing a network boot the interface is already active, so it can't be renamed.

Passing net.ifnames=0 to the kernel will stop systemd renaming the interfaces.  Maybe we just want to enable this for the qemu machines as they'll generally only have one interface anyway.

Comment 3 Stefan Stanacar 2013-08-08 12:57:23 UTC

This is the old qemuimagetest, no longer running on AB. The new testimage has that message whitelisted in the dmesg test.