Busted Gemfile?

Hi,
I was having trouble getting foreman-1.1RC5 to work. The error
mentioned the 'puppet master configprint' command, so I thought it was
the issue mentioned in the wiki. I have a nonstandard puppet master
config, so I updated /etc/foreman/settings.yaml, but the problem
persisted. Looking closer, the error mentioned that 'puppet is not
part of the bundle'. I am not a ruby guy, so this does not mean much
to me.

After piddling around, what I discovered was that if I added

gem 'puppet'

to /usr/share/foreman/Gemfile, everything works.

So I know other folks don't have the same issue, so why might adding
that line be necessary for me? I did fight a few rounds with local
gems, so something might have gone a little wonky, but what might that
be?

··· -- Chad M. Huneycutt

> Hi,
> I was having trouble getting foreman-1.1RC5 to work. The error
> mentioned the 'puppet master configprint' command, so I thought it was
> the issue mentioned in the wiki. I have a nonstandard puppet master
> config, so I updated /etc/foreman/settings.yaml, but the problem
> persisted. Looking closer, the error mentioned that 'puppet is not
> part of the bundle'. I am not a ruby guy, so this does not mean much
> to me.
>
> After piddling around, what I discovered was that if I added
>
> gem 'puppet'

OK 1) You shouldn't need to do this, as it should pick up puppet from
other sources.
2) If you do do this, please add a version string… or you risk
unforeseen issues, if the worng version of puppet is installed.
3) put the change in ./bundler.d/Gemfile.local.rb rather than editting
the Gemfile directly.

··· On Wed, Jan 30, 2013 at 9:00 PM, Chad Huneycutt wrote:

to /usr/share/foreman/Gemfile, everything works.

So I know other folks don’t have the same issue, so why might adding
that line be necessary for me? I did fight a few rounds with local
gems, so something might have gone a little wonky, but what might that
be?


Chad M. Huneycutt


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

So I fixed it. I am not entirely sure what the problem is, but I
reinstalled puppet, facter, and hiera. As I mentioned, I screwed up
and used gem directly, trying to get librarian-puppet installed, and
when I tried to undo the damage, I noticed that it removed some stuff
that was shared with the rpms. I can only guess that the gem removed
something that bundler used to find puppet, and reinstalling the
package put it back.

Anyway, maybe this will be helpful to someone some day…

··· On Thu, Jan 31, 2013 at 12:00 AM, Chad Huneycutt wrote: > Hi, > I was having trouble getting foreman-1.1RC5 to work. The error > mentioned the 'puppet master configprint' command, so I thought it was > the issue mentioned in the wiki. I have a nonstandard puppet master > config, so I updated /etc/foreman/settings.yaml, but the problem > persisted. Looking closer, the error mentioned that 'puppet is not > part of the bundle'. I am not a ruby guy, so this does not mean much > to me. > > After piddling around, what I discovered was that if I added > > gem 'puppet' > > to /usr/share/foreman/Gemfile, everything works. > > So I know other folks don't have the same issue, so why might adding > that line be necessary for me? I did fight a few rounds with local > gems, so something might have gone a little wonky, but what might that > be? > > -- > Chad M. Huneycutt


Chad M. Huneycutt