New issue
Advanced search Search tips

Issue 748115 link

Starred by 0 users

Issue metadata

Status: Archived
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 702007



Sign in to add a comment

whirlwind testbed-ap wireless-4.2 reboot / shutdown fails

Project Member Reported by ecgh@chromium.org, Jul 24 2017

Issue description

Reboot succeeds with current (Jan 2016) stable lab image (trybot-whirlwind-test-ap/R50-7849.0.0-b13) but fails with new whirlwind testbed-ap wireless-4.2 build.
 

Comment 1 by ecgh@chromium.org, Jul 27 2017

Reboot/shutdown was hanging because ui-post-stop was stuck in "while ! sudo -u chronos kill -9 -- -1 ; do" loop because cros_embedded's sudo-to-su wrapper doesn't handle -u.

UI is coming from chromeos-base/chromeos-login, which is pulled in by chromeos-base/debugd.

So fix for reboot is to remove UI by removing debugd.
Cc: briannorris@chromium.org
Components: OS>Packages
Labels: OS-Chrome
I see the jetstream overlay already disables the debugd USE flag (as do several other embedded targets). Could be OK to do the same.

What's pulling in debugd? Just the defaults in target-chromium-os? Would all 'embedded' profiles be broken, if they don't explicitly disable debugd?
Additionally, jetstream actually *enables* a proper sudo:

# Use pam so that sudo is pulled in properly.
USE="${USE} pam"

And I note that the existing images have *no* debugd (or chromeos-login), but they *do* have 'pam' (and therefore sudo).

Comment 4 by ecgh@chromium.org, Jul 31 2017

I believe debugd is coming from the target-chromium-os defaults.
I'm testing out a change to do USE="${USE} -debugd" in overlay-whirlwind-private's make.defaults (like -transparent_hugepage).
I could pull in real sudo. That would match normal whirlwind more closely, although then I might have missed the fact that debugd and login UI needed to be removed.
Cc: vapier@chromium.org
Yeah, testing with USE="-debugd" seems like the right approach.

I wonder if debugd should just be removed in the base embedded feature profile, since it makes the default build (i.e., without USE=pam) broken. And many profiles end up manually fixing this up anyway, often by disabling debugd themselves.

We could figure out the sudo question independently; it seems like we should definitely at least avoid the chromeos-login dependency, if not the entirety of debugd.
we should either extend our dumb wrapper to handle -u, or just throw it away and always install the full sudo.  i'd lean towards doing that now.

the sudo/pam binding has larger been cleaned now with the move to chromeos-auth-config
as for the debugd->chromeos-login dep, that should get resolved.  perhaps by just deleting it.
Project Member

Comment 8 by bugdroid1@chromium.org, Aug 9 2017

I filed this to follow up on the chromeos-login vs. fake sudo conflict:

https://bugs.chromium.org/p/chromium/issues/detail?id=753626

Comment 10 by ecgh@chromium.org, Aug 18 2017

Status: Fixed (was: Started)

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

Status: Archived (was: Fixed)

Sign in to add a comment