cros_sdk MountChroot fails on Fedora 27 x86_64

[scott worley]

Hi,

I'm setting up a ChromiumOS development environment on Fedora linux.  Previously on Fedora 26 entering the chroot via cros_sdk had no issues.  Fedora 27 has changed something and I get an error from cros_sdk in MountChroot.  It takes running cros_sdk multiple times before it works.  Any clues how I can debug this?

Thanks,

Scott

$ cros_sdk

cros_sdk: Unhandled exception:

Traceback (most recent call last):

  File "/home/non/chromiumos/chromite/bin/cros_sdk", line 169, in <module>

    DoMain()

  File "/home/non/chromiumos/chromite/bin/cros_sdk", line 165, in DoMain

    commandline.ScriptWrapperMain(FindTarget)

  File "/home/non/chromiumos/chromite/lib/commandline.py", line 911, in ScriptWrapperMain

    ret = target(argv[1:])

  File "/home/non/chromiumos/chromite/scripts/cros_sdk.py", line 932, in main

    cros_build_lib.MountChroot(options.chroot, create=False)

  File "/home/non/chromiumos/chromite/lib/cros_build_lib.py", line 1648, in MountChroot

    SudoRunCommand(cmd, capture_output=True, print_cmd=False)

  File "/home/non/chromiumos/chromite/lib/cros_build_lib.py", line 290, in SudoRunCommand

    return RunCommand(cmd, **kwargs)

  File "/home/non/chromiumos/chromite/lib/cros_build_lib.py", line 654, in RunCommand

    raise RunCommandError(msg, cmd_result)

chromite.lib.cros_build_lib.RunCommandError: return code: 32; command: mount -text4 -onoatime /dev/cros_home+non+chromiumos+chroot_000/chroot /home/non/chromiumos/chroot

mount: /home/non/chromiumos/chroot: special device /dev/cros_home+non+chromiumos+chroot_000/chroot does not exist.

cmd=['mount', '-text4', '-onoatime', '/dev/cros_home+non+chromiumos+chroot_000/chroot', '/home/non/chromiumos/chroot']

[Mike Frysinger]

you can pass --nouse-image to avoid all the image related logic

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[scott worley]

Thanks!  --nouse-image worked.

[Marc Herbert]

BTW this thread provides good background information about the recent --[no]use-image feature:

https://groups.google.com/a/chromium.org/d/msg/chromium-os-dev/yVEWDR7wDfA/LSZZ8RG6AgAJ

One thing I couldn't find there though is whether --nouse-image will keep being supported and if yes for how long?

[Mike Frysinger]

running w/out an image will always be an option

-mike