Issue metadata
Sign in to add a comment
|
CQ and Developer errors related to glibc uprev |
||||||||||||||||||||||||
Issue descriptionSeveral builders in this CQ run fail related to glibc version: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930322222167225344 One example failed in InitSDK: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930321079381969632 Some packages failed in BuildPackages https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8930321054708458272/+/steps/BuildPackages/0/stdout (backports-lzma looks glibc related. Not so sure about nss) Likely fallout from https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1296797
,
Nov 9
,
Nov 9
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?
,
Nov 9
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
,
Nov 9
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.
,
Nov 12
Changed to P2 since chroot hook has been submitted.
,
Nov 12
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.
,
Nov 12
Closing the bug, please re-open if the instructions in #4 are not enough to recover the chroot.
,
Nov 16
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.
,
Nov 16
> 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 |
|||||||||||||||||||||||||
Comment 1 by ddavenp...@chromium.org
, Nov 9