| Summary: |
Build Appliance has no network - connman doesn't manage eth interfaces on qemu machines |
| Product: |
[Build System, Metadata & Runtime] Runtime
|
Reporter: |
Stefan Stanacar <sstncr> |
| Component: |
build-appliance | Assignee: |
Cristian Iorga <cristian.iorga> |
| Status: |
VERIFIED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium+
|
CC: |
sgw
|
| Version: |
1.4 | |
|
| Target Milestone: |
1.4 M4 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
---
|
|---|
| Bug Depends on: |
3227
|
|
|
| Bug Blocks: |
|
|
|
Steps: - bitbake and boot build-appliance-image (using 1.4M3.rc1 or rc2 release) Expected results: - VM should have access to the network The VM doesn't have network because connman doesn't manage ethX interfaces anymore. This was tricky to notice at first because a minimal build works in Hob (it has sources pre-fetched). Commit 7048fbdc05c1f2d9acaf1052550dec792c1f18da introduces connman-conf recipe for all qemu machines, which installs a config for connman, blacklisting all eth* interfaces. Blacklisting eth interfaces affects build appliance image too (because it's built as qemux86-64 machine usually). Ugly fix (tested): diff --git a/meta/recipes-core/images/build-appliance-image.bb b/meta/recipes-core/images/build-appliance-image.bb index 2359eca..b8255ac 100644 --- a/meta/recipes-core/images/build-appliance-image.bb +++ b/meta/recipes-core/images/build-appliance-image.bb @@ -64,6 +64,8 @@ fakeroot do_populate_poky_src () { # Use Clearlooks GTK+ theme mkdir -p ${IMAGE_ROOTFS}/etc/gtk-2.0 echo 'gtk-theme-name = "Clearlooks"' > ${IMAGE_ROOTFS}/etc/gtk-2.0/gtkrc + + rm -f ${IMAGE_ROOTFS}/etc/connman/main.conf } IMAGE_PREPROCESS_COMMAND += "do_populate_poky_src; "