New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767907 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

qemu is failing to build on chromiumos-sdk (gid conflict)

Project Member Reported by manojgupta@chromium.org, Sep 22 2017

Issue description

https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8142/steps/InitSDK/logs/stdio

qemu-2.6.0-r1: >>> Running pre-merge checks for app-emulation/qemu-2.6.0-r1
qemu-2.6.0-r1:  * Determining the location of the kernel source code
qemu-2.6.0-r1:  * Unable to find kernel sources at /usr/src/linux
qemu-2.6.0-r1:  * Please make sure that /usr/src/linux points at your running kernel, 
qemu-2.6.0-r1:  * (or the kernel you wish to build against).
qemu-2.6.0-r1:  * Alternatively, set the KERNEL_DIR environment variable to the kernel sources location
qemu-2.6.0-r1:  * Unable to calculate Linux Kernel version for build, attempting to use running version
qemu-2.6.0-r1:  * Unable to check your kernel for KVM support
qemu-2.6.0-r1: >>> Emerging (1 of 1) app-emulation/qemu-2.6.0-r1::chromiumos
qemu-2.6.0-r1:  * qemu-2.6.0.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...               [ ok ]
qemu-2.6.0-r1:  * Running stacked hooks for pre_pkg_setup
qemu-2.6.0-r1:  *    sysroot_build_bin_dir ...
qemu-2.6.0-r1:  [ ok ]
qemu-2.6.0-r1:  * Adding /mnt/host/source/src/third_party/eclass-overlay/profiles/base/accounts to user/group search path.
qemu-2.6.0-r1:  * Adding group 'kvm' to your system ...
qemu-2.6.0-r1:  * 78 conflicts with provided 409!
qemu-2.6.0-r1:  * ERROR: app-emulation/qemu-2.6.0-r1::chromiumos failed (setup phase):
qemu-2.6.0-r1:  *   78 conflicts with provided 409!
qemu-2.6.0-r1:  * 
qemu-2.6.0-r1:  * Call stack:
qemu-2.6.0-r1:  *              ebuild.sh, line  93:  Called pkg_setup
qemu-2.6.0-r1:  *   qemu-2.6.0-r1.ebuild, line 275:  Called enewgroup 'kvm' '78'
qemu-2.6.0-r1:  *            user.eclass, line 474:  Called die
qemu-2.6.0-r1:  * The specific snippet of code:
qemu-2.6.0-r1:  *   			die "${egid} conflicts with provided ${provided_gid}!"

This is breaking chromiumos-sdk builder.

The breaking CL commit time range is within Thu, Sep 21 6pm to Friday, Sep 22 6am.
 
Components: Infra>Client>ChromeOS
Owner: cernekee@chromium.org
+cernekee did you make any qemu changes?
Sweet, looks like my new qemu package is getting deployed. :-)

The two changes were:

1) Move it from portage-stable to chromiumos_overlay
2) Add a local patch + revbump

It is the same version as before, and I didn't change any uids/gids.

> qemu-2.6.0-r1:  * ERROR: app-emulation/qemu-2.6.0-r1::chromiumos failed (setup phase):
> qemu-2.6.0-r1:  *   78 conflicts with provided 409!

The ebuild says:

+pkg_setup() {
+       enewgroup kvm 78
+}

Do we know where "409" is coming from?  There's nothing relevant when I `grep -E "\<409\>"` in chromiumos_overlay.  My own chroot is still using 409 after installing the new 2.6.0-r1 ebuild.
I have no idea if this is the right fix, but I'll put it out there in case it helps:

http://crosreview.com/678857
> Can you launch a chromiumos-sdk tryjob to verify?

$ cbuildbot --remote chromiumos-sdk

No patches were provided; are you sure you want to just run a remote build of ToT? (yes/No)? yes
Verifying patches...
Submitting tryjob...
Successfully sent PUT request to [buildbucket_bucket:master.chromiumos.tryserver] with [config:chromiumos-sdk] [buildbucket_id:8967731737920235792].
Tryjob submitted!
Go to https://uberchromegw.corp.google.com/i/chromiumos.tryserver/waterfall?committer=cernekee@chromium.org&builder=etc to view the status of your job.


I don't see anything in the web interface yet.
Don't you need to specify the CL? i.e. -g 678857. 

The tryjob can be tracked at 
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chromiumos-sdk (Pending right now?)


Project Member

Comment 7 by bugdroid1@chromium.org, Sep 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/557d72e90a8db8f634aff04a55acd54acaa72b17

commit 557d72e90a8db8f634aff04a55acd54acaa72b17
Author: Kevin Cernekee <cernekee@chromium.org>
Date: Fri Sep 22 19:59:48 2017

app-emulation/qemu: Don't force gid 78 for 'kvm' group

Our installations use gid 409, so this may create a conflict.

BUG= chromium:767907 
TEST=`sudo emerge qemu`

Change-Id: Icbeb1d956316261476cc47de64ca4a8871a302b8
Reviewed-on: https://chromium-review.googlesource.com/678857
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Kevin Cernekee <cernekee@chromium.org>

[modify] https://crrev.com/557d72e90a8db8f634aff04a55acd54acaa72b17/app-emulation/qemu/qemu-2.6.0.ebuild
[rename] https://crrev.com/557d72e90a8db8f634aff04a55acd54acaa72b17/app-emulation/qemu/qemu-2.6.0-r2.ebuild

Status: Fixed (was: Untriaged)

Comment 9 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 10 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment