Uploaded image for project: 'R10K'
  1. R10K
  2. RK-325

'can't find gem r10k' error in 2019.0.x

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Froyo
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Our pe-r10k pipelines are failing:

      https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/job/enterprise_pe-r10k-vanagon_pkg-int-sys-testing_daily-johnson/CLIENT_TEST_TARGET=ubuntu1604-64.mdca,CT_COMPONENT=rubygem_r10k,GIT_PROVIDER=rugged,SLAVE_LABEL=beaker/16/console 

      with:

      Beaker::Host::CommandFailure: Host 'ptsmq4pzhjofs05.delivery.puppetlabs.net' exited with 1 running:
      12:57:37  /opt/puppetlabs/puppet/bin/r10k deploy environment -v
      12:57:37 Last 10 lines of output were:
      12:57:37 	/opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems.rb:271:in `find_spec_for_exe': can't find gem r10k (>= 0.a) (Gem::GemNotFoundException)
      12:57:37 		from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems.rb:299:in `activate_bin_path'
      12:57:37 		from /opt/puppetlabs/puppet/bin/r10k:23:in `<main>'
      

       

      I can see that we set the gempath to ruby 2.5.0:

      https://github.com/puppetlabs/pe-r10k-vanagon/commit/6c51de8e69a50ece0cd1d0b7a027987bcd4f4817

      ("/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/")

      But above we are looking in /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems.rb

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amy.sahli Amy Sahli
              Reporter:
              amy.sahli Amy Sahli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support