Project

General

Profile

Actions

Bug #10561

open

sometimes `arvbox reboot test` gets stuck asking for a sudo password

Added by Joshua Randall over 7 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Story points:
-
Release:
Release relationship:
Auto

Description

I don't know what causes this problem, but sometimes for me a run of `arvbox reboot test` gets stuck asking for a sudo password, seemingly because it is trying to install dependencies in a system directory (/var/lib/gems) but is running as the arvbox user that doesn't have permission to do that. Probably it should be installing all of the dependencies into /var/lib/arvados/test/GEMHOME?

Will install dependencies to /var/lib/gems
Will install arvados gems to /var/lib/arvados/test/GEMHOME/.gem/ruby/2.1.0
Gem search path is GEM_PATH=/var/lib/arvados/test/GEMHOME/.gem/ruby/2.1.0:/var/lib/gems
PATH is /var/lib/arvados/test/GEMHOME/.gem/ruby/2.1.0/bin:/var/lib/gems/bin:/var/lib/arvados/test/VENVDIR/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/var/lib/gems/bin

                   ********** Running doc install **********

(Running bundle install --local. 'could not find package' messages are OK.)
Installing rake 10.1.1

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Your user account isn't allowed to install to the system Rubygems.
  You can cancel this installation and run:

      bundle install --path vendor/bundle

  to install the gems into ./vendor/bundle/, or you can enter your password
  and install the bundled gems to Rubygems using sudo.

  Password:
Actions #1

Updated by Joshua Randall over 7 years ago

It seems like this happens if I try to run `arvbox reboot test` to create an arvbox from scratch (i.e. immediately after destroying it).

If I run `arvbox reboot test` after `arvbox reboot dev`, I don't seem to run into this problem.

Actions #2

Updated by Tom Morris over 6 years ago

  • Target version set to Arvados Future Sprints
Actions #3

Updated by Ward Vandewege almost 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions #4

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions #5

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF