Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-4815

Puppetserver_gem : source option does not work as expected

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • puppetserver_gem
    • None
    • Needs Assessment

    Description

      Basic Info
      Module Version: puppetserver_gem forge module 0.2.0
      Puppet Version: puppetserver 2.2.0
      OS Name/Version: RHEL 6.5

      If you use the source option for an install it gets added to the puppetserver gem command line before any install_options which means that you cannot use clear-sources and so rubygems.org is always searched first. The need for this is illustrated from the following puppetserver gem command lines:

      myhost:~ # puppetserver gem install jmx --version 1.0 --no-document --clear-sources --source https://my-internal-gem-repo/default.gems.global/
      Successfully installed jmx-1.0
      1 gem installed
      myhost:~ # puppetserver gem uninstall jmx
      Successfully uninstalled jmx-1.0
      myhost:~ # puppetserver gem install jmx --version 1.0 --no-document --source https://my-internal-gem-repo/default.gems.global/ --clear-sources 
      ERROR:  Could not find a valid gem 'jmx' (= 1.0), here is why:
                Unable to download data from https://rubygems.org/ - Errno::ECONNREFUSED: Connection refused - Connection refused (https://api.rubygems.org/specs.4.8.gz)
      

      Desired Behavior:
      Adding clear-sources to install_options should put it on the gem command line before the source option.

      Actual Behavior:

      Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              elaps Alan Schwarzenberger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support