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

Issue 903855 link

Starred by 4 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Build-Toolchain



Sign in to add a comment

CQ and Developer errors related to glibc uprev

Project Member Reported by ddavenp...@chromium.org, Nov 9

Issue description

This is also affecting developers, even after syncing to https://chromium-review.googlesource.com/c/1329581


build_packages fails with the following:
python2: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/libpython2.7.so.1.0)

The same error is also seen upon entering the chroot
Summary: CQ and Developer errors related to glibc uprev (was: CQ failures related to glibc uprev)
Cc: vapier@chromium.org
Labels: OS-Chrome
If the chroot python is broken, I am not sure it is even possible to run update_chroot.

Root cause was update_chroot didn't update sys-libc/glibc but probably  updated other packages including python. 

While https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1329581 has fixed the update_chroot problem, update_chroot can't be run because of python issues.

Vapier@: what do you suggest? How can python be repaired. Is there a way to force update glibc without touching python?
Possible workaround if python is broken is to update glibc files manually:

Should be done outside the chroot:

$ gsutil cp gs://chromeos-prebuilt/board/amd64-host/chroot-2018.11.08.122731/packages/sys-libs/glibc-2.27-r6.tbz2 /tmp

$ cd /path/to/checkout/chroot
$ tar -jxvf /tmp/glibc-2.27-r6.tbz2
Components: Infra>Client>ChromeOS>Build
i think the cros_setup_toolchains logic in update_chroot somewhat took care of this, but overall we don't track ABI deps at this level (ELF version info from SONAMEs), and it's largely been OK.  you could argue that glibc is just one example of the common problem.

adding an upgrade hook as Manoj did should mitigate it in this case.
Components: Tools>ChromeOS-Toolchain
Labels: -Pri-1 Pri-2
Status: Assigned (was: Untriaged)
Changed to P2 since chroot hook has been submitted.
if the hook was sufficient to recover bots/devs, i'd close this out.  if we want to track the general problem (comment #5), prob want to start a new bug to brainstorm.
Status: Verified (was: Assigned)
Closing the bug, please re-open if the instructions in #4 are not enough to recover the chroot.
I have gblic error on the DUT when upgrading from 71 to 72:

stateful (an /usr/local) comes from 72 but image is from 71:
localhost ~ # python
python: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/local/lib64/libpython2.7.so.1.0)

chromeos-install fixes the issue.


screen-exchange
28.5 KB View Download
> stateful (an /usr/local) comes from 72 but image is from 71:

that isn't supported and never really has been.  you need to reimage your device.

Sign in to add a comment