On Fri, Nov 16, 2012 at 10:55 PM, Asif Iqbal wrote:
> On Wed, Nov 14, 2012 at 6:18 PM, Jeff McCune wrote:
>>
>> On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal wrote:
>> >
>> > Here is another simple one
>> >
>> > # puppet apply --trace --evaltrace -e 'user {"dummy": ensure =>
>> > present}'
>> >
>
On Fri, Nov 16, 2012 at 10:55 PM, Asif Iqbal wrote:
>
>
>
> On Wed, Nov 14, 2012 at 6:18 PM, Jeff McCune wrote:
>
>> On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal wrote:
>> >
>> > Here is another simple one
>> >
>> > # puppet apply --trace --evaltrace -e 'user {"dummy": ensure =>
>> present}'
>>
On Wed, Nov 14, 2012 at 6:18 PM, Jeff McCune wrote:
> On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal wrote:
> >
> > Here is another simple one
> >
> > # puppet apply --trace --evaltrace -e 'user {"dummy": ensure =>
> present}'
> >
> > http://paste.ubuntu.com/1344435/
>
> These definitely seem lik
On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal wrote:
>
> Here is another simple one
>
> # puppet apply --trace --evaltrace -e 'user {"dummy": ensure => present}'
>
> http://paste.ubuntu.com/1344435/
These definitely seem like bugs. Could you please file a bug report
at http://projects.puppetlabs
On Fri, Nov 9, 2012 at 12:08 AM, Asif Iqbal wrote:
>
>
> On Thu, Nov 8, 2012 at 4:34 PM, Jeff McCune wrote:
>
>> Could you add --trace and --evaltrace to whatever command you're
>> executing that gives the error, then paste the command and the output?
>
>
> http://paste.ubuntu.com/1344430/
>
>
>
On Thu, Nov 8, 2012 at 4:34 PM, Jeff McCune wrote:
> Could you add --trace and --evaltrace to whatever command you're executing
> that gives the error, then paste the command and the output?
http://paste.ubuntu.com/1344430/
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because
OK, this definitely looks like a problem with Puppet.
Could you add --trace and --evaltrace to whatever command you're executing
that gives the error, then paste the command and the output?
Thanks,
-Jeff
On Thu, Nov 8, 2012 at 12:12 PM, Asif Iqbal wrote:
>
>
> On Thu, Nov 8, 2012 at 12:43 PM,
On Thu, Nov 8, 2012 at 12:43 PM, Jeff McCune wrote:
> ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d|
> $LOAD_PATH.collect {|l| { l => Dir["#{l}/#{d}/**/*.rb"] }}}.to_yaml'
http://paste.ubuntu.com/1343465/
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes
On Wed, Nov 7, 2012 at 6:55 PM, Asif Iqbal wrote:
>
> yep, It does look like I have two different ruby
>
Not necessarily, these are just all of the directories a single ruby
executable will look to when trying to load *.rb files using the 'require'
statement.
/usr/local/lib/site_ruby
>
Looking
On Wed, Nov 7, 2012 at 9:51 PM, Asif Iqbal wrote:
>
>
>
> On Wed, Nov 7, 2012 at 4:18 PM, Jeff McCune wrote:
>
>> On Tue, Nov 6, 2012 at 7:08 PM, Asif Iqbal wrote:
>>
>>> I did some clean up. Now I have only one version of puppet and facter.
>>
>>
>> It still seems like you could have stale fil
On Wed, Nov 7, 2012 at 4:18 PM, Jeff McCune wrote:
> On Tue, Nov 6, 2012 at 7:08 PM, Asif Iqbal wrote:
>
>> I did some clean up. Now I have only one version of puppet and facter.
>
>
> It still seems like you could have stale files.
>
> Could you verify there are no stale files by pasting the ou
On Tue, Nov 6, 2012 at 7:08 PM, Asif Iqbal wrote:
> I did some clean up. Now I have only one version of puppet and facter.
It still seems like you could have stale files.
Could you verify there are no stale files by pasting the output of this
command?
ruby -r puppet -e 'puts %w{ puppet facter
I did some clean up. Now I have only one version of puppet and facter.
$ dpkg -S facter
http://paste.ubuntu.com/1338890/
$ dpkg -l facter
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Statu
It looks to me as if there are at least two facters installed. One was
likely installed using install.rb (probably the one in
/usr/local/lib/site_ruby), and another was installed using the package
manager. Can you post the output of both `dpkg -S facter` and `dpkg -l
facter`? That will show which w
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza wrote:
> What version(s) of facter are you running? Perhaps you have multiple
> installed here as well? It seems strange that the trace you posted
> references two distinct library paths,
> e.g.
> /usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal
On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune wrote:
> Did you have a version of Puppet on this system previously? This
> definitely seems like a bug, but it seems like one that only manifests if
> there's some other copy of Puppet that is also being loaded along with the
> version you expect.
>
>
Did you have a version of Puppet on this system previously? This
definitely seems like a bug, but it seems like one that only manifests if
there's some other copy of Puppet that is also being loaded along with the
version you expect.
-Jeff
On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal wrote:
> O
On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal wrote:
> I am getting this error after installing puppet with gem
>
> $ gem install puppet
> Fetching: facter-1.6.14.gem (100%)
> Fetching: puppet-3.0.1.gem (100%)
> Successfully installed facter-1.6.14
> Successfully installed puppet-3.0.1
> 2 gems ins
19 matches
Mail list logo
