Hi Eric,
Thank you. I filled in some more detail, and started following the bug.
Let's continue there.
Cheers,
Paul
On Thursday, October 4, 2012 4:01:28 AM UTC+3, Eric Sorenson wrote:
>
> Hi Paul, I created a ticket to track this issue, thanks for posting the
> trace output and manifest.
>
> h
Hi Paul, I created a ticket to track this issue, thanks for posting the
trace output and manifest.
http://projects.puppetlabs.com/issues/16772
-=Eric
On Wednesday, October 3, 2012 6:27:41 AM UTC-7, Paul Tötterman wrote:
>
> > Ubuntu released a backport of 0.3.0 into lucid-backports which will
> Ubuntu released a backport of 0.3.0 into lucid-backports which will
> resolve the issue for you here:
> http://packages.ubuntu.com/lucid-backports/libaugeas-ruby
Unfortunately upgrading the package did not solve the problem. Also the
error message doesn't match the bug report.
--trace gives
On 02/10/12 14:49, Paul Tötterman wrote:
> Hi,
>
> My manifests used to work with 2.7.19 but after upgrading to 3.0.0 I
> keep getting:
>
> Error: /Stage[main]/.../Augeas[...]: Could not evaluate: uninitialized
> constant Augeas::NO_LOAD
This will be a dependency on ruby-augeas 0.3.0 or higher.
On Tue, Oct 2, 2012 at 6:49 AM, Paul Tötterman wrote:
> Hi,
>
> My manifests used to work with 2.7.19 but after upgrading to 3.0.0 I
> keep getting:
Did you upgrade only the agent, or the master to 3.0.0 before
upgrading any agents?
> Error: /Stage[main]/.../Augeas[...]: Could not evaluate: unin
Hi,
My manifests used to work with 2.7.19 but after upgrading to 3.0.0 I
keep getting:
Error: /Stage[main]/.../Augeas[...]: Could not evaluate: uninitialized
constant Augeas::NO_LOAD
Anyone else had and solved this problem? On precise I just get:
Warning: Augeas[...](provider=augeas): Loading f
