Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-263

puppetserver gem install fails in an unexpected manner when run unprivileged

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: SERVER 1.0.0
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:

      Description

      Just a yak to shave that I ran into...

      When running `puppetserver gem install pry` as a normal user, I'd expect the gem to be installed into my home directory, or an error message that my user account does not have permission to install gems into the system location.

      Instead I get the following error, which I suspect is related to mishandling the {{

      {HOME}

      }} environment variable.

      [vagrant@localhost ~]$ puppetserver gem install pry
      Fetching: coderay-1.1.0.gem (100%)
      ERROR:  While executing gem ... (Errno::ENOENT)
          No such file or directory - /.gem/jruby/1.9/cache/coderay-1.1.0.gem
      [vagrant@localhost ~]$ echo $HOME
      /home/vagrant
      

      Installing as root works:

      [vagrant@localhost ~]$ sudo puppetserver gem install pry
      Fetching: coderay-1.1.0.gem (100%)
      Successfully installed coderay-1.1.0
      Fetching: slop-3.6.0.gem (100%)
      Successfully installed slop-3.6.0
      Fetching: method_source-0.8.2.gem (100%)
      Successfully installed method_source-0.8.2
      Fetching: spoon-0.0.4.gem (100%)
      Successfully installed spoon-0.0.4
      Fetching: pry-0.10.1-java.gem (100%)
      Successfully installed pry-0.10.1-java
      5 gems installed
      

      [vagrant@localhost ~]$ sudo puppetserver gem which pry
      /var/lib/puppet/jruby-gems/gems/pry-0.10.1-java/lib/pry.rb
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jeff Jeff McCune
                QA Contact:
                Erik Dasher
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support