Bug #10990

gems.erb cloudpack script contains incorrect (nonworking) yum repository

Added by Chris MacLeod 6 months ago. Updated 6 months ago.

Status:Investigating Start date:11/21/2011
Priority:Normal Due date:
Assignee:Kelsey Hightower % Done:

0%
Category:cloudpack Spent time: -
Target version:-
Keywords: Branch:
Votes: 0

Description

./lib/puppet/cloudpack/scripts/gems.erb in the cloud_provisioner puppet module creates a repository called ‘epel’ that references the ‘prosvc’ yum repository for puppetlabs professional services. The repo 1) doesn’t work 2) isn’t epel and should be marked as so (potentially overriding a pre-configured epel repository).

History

#1
Updated by Kelsey Hightower 6 months ago

  • Category set to cloudpack
  • Status changed from Unreviewed to Investigating
  • Assignee set to Kelsey Hightower

Chris,

Thanks for reporting this issue. I have a couple of questions:

  • What version of CP are you using?
  • Also, can you provide the command you are running?

#2
Updated by Kelsey Hightower 6 months ago

The gems script has been replace with a new puppet-community script, which make use of the yum.puppetlabs.com repository. This change also removes the dependance on EPEL.

The switch to puppet-community from gems was made in the master branch here: bef11acfbaec0961b805a2a2203a16e68265045d

Now, I need to figure out the next release for CP.

#3
Updated by Chris MacLeod 6 months ago

version ‘0.6.0rc1’ (From the Modulefile). It was the version installed via puppet-module.

puppet node bootstrap —image ami-2342a94a —type t1.micro —keypair [keypair] —keyfile ~/.ssh/[keyfile] —login root

Also available in: Atom PDF