Issue metadata
Sign in to add a comment
|
cros deploy failing to push the package to Jetstream devices |
||||||||||||||||||||||
Issue descriptionChrome Version: Issue observed on ToT CHROMEOS_RELEASE_DESCRIPTION=11523.0.2019_01_04_1628 (Test Build - ratheeshs) developer-build gale OS: Linux Error seen during cros deploy (Complete Verbose log attached): !!! Unable to parse profile: '/usr/local/etc/portage/make.profile' !!! ParseError: Parent '/etc/portage/make.profile' not found: '/usr/local/etc/portage/make.profile/parent' !!! Problem with sandbox binary. Disabling... !!! Your current profile is invalid. If you have just changed your profile !!! configuration, you should revert back to the previous configuration. !!! Allowed actions are limited to --help, --info, --search, --sync, and !!! --version. What steps will reproduce the problem? (1) Flash the compiled ToT image(chromiumos_test_image.bin) to Jetstream device (2) After flashing, do cros deploy <ip> ap-daemons What is the expected result? Cros deploy should successfully push the package. What happens instead? Cros deploy fails to push the package mentioned. If this is a regression
,
Jan 7
I built gale locally last week and /etc/portage/make.profile existed, but was a symbolic link to a path that is only valid in the chroot. IIRC on actual device images this symlink is typically replaced by a copy of the profile.
,
Jan 8
The NextAction date has arrived: 2019-01-08
,
Jan 8
I just mounted a gale image and /etc/portage doesn't exist. We could change the gmerge ebuild to sync the profile from the build root (/board/gale/etc/portage/) to the profile that will be used on the device in /usr/local.
,
Jan 8
It looks like that would be created by: chromeos-base/dev-install
,
Jan 8
yes, systems need to have chromeos-base/dev-install in order to work. if it worked before by accident, well that's good, but we just got lucky. lets pull it out of USE=!cros_embedded in virtual/target-chromium-os/target-chromium-os-1.ebuild so it's always enabled for all systems
,
Jan 10
After flashing an image that installs chromeos-base/dev-install, it seems cros deploy will still silently fail to deploy changes.
,
Jan 10
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/011b6699e055ba423631547db17ef33394cf65f8 commit 011b6699e055ba423631547db17ef33394cf65f8 Author: Mike Frysinger <vapier@chromium.org> Date: Thu Jan 10 21:58:38 2019 target-chromium-os: make dev-install available everywhere We rely on this for people to use `cros deploy`, so add this to the default OS target for everyone. It's a small package (<50KiB), so it shouldn't have a huge impact on people. BUG= chromium:919594 TEST=precq passes Change-Id: Iafe04690ff306b70d9e913cad59768e2e647909a Reviewed-on: https://chromium-review.googlesource.com/1401142 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Allen Webb <allenwebb@google.com> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Edward Jee <edjee@google.com> Reviewed-by: Allen Webb <allenwebb@google.com> [modify] https://crrev.com/011b6699e055ba423631547db17ef33394cf65f8/virtual/target-chromium-os/target-chromium-os-1.ebuild [rename] https://crrev.com/011b6699e055ba423631547db17ef33394cf65f8/virtual/target-chromium-os/target-chromium-os-1-r114.ebuild
,
Jan 11
mgild@google.com Will you post verbose logs for cros deploy?
,
Jan 11
Output of `cros deploy ${DUT_IP} ap-daemons --debug` found here:
https://paste.googleplex.com/4649442670018560?raw
Looks like this is associated with https://bugs.chromium.org/p/chromium/issues/detail?id=920140
,
Jan 11
Confirmed that the workaround listed in https://bugs.chromium.org/p/chromium/issues/detail?id=920140 fixes cros deploy.
,
Jan 11
i think this issue is resolved now |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ratheeshs@google.com
, Jan 7