[augeas-devel] Warning: Augeas 0.10.0 + Puppet issue

[Raphaël Pinson]

Thanks for the patches.

I have applied them in Ubuntu precise:

https://launchpad.net/ubuntu/precise/+source/puppet/2.7.6-1ubuntu1


Raphaël


On Tue, Dec 20, 2011 at 12:10 AM, Dominic Cleal <dcleal at redhat.com> wrote:
> Hi folks,
>
> A heads up if you're using Puppet and intend to upgrade to Augeas 0.10.0
> - there's a bug in the provider where it doesn't do version comparisons
> correctly.
>
>  http://projects.puppetlabs.com/issues/show/11414
>
> The provider does string comparisons on the Augeas version number, it
> assumes that 0.10.0 < 0.3.6 and doesn't follow the normal code path for
> recent Augeas versions.
>
> Unfortunately a bug in the 2.7.x fallback code meant that won't save
> changes either.  Puppet 2.6.x and earlier will save, but resources will
> show as out of sync and "execute" on every run.
>
> For Puppet 2.7.x, you could apply the following patches to your
> augeas.rb provider:
>  https://github.com/domcleal/puppet/commit/3239ab3f.patch
>  https://github.com/domcleal/puppet/commit/735acad5.patch
>
> Complete 2.7.x augeas.rb file:
>
> https://github.com/domcleal/puppet/blob/735acad5/lib/puppet/provider/augeas/augeas.rb
>
> Puppet 2.6.x patch:
>  https://github.com/domcleal/puppet/commit/e3fc5c49.patch
>
> In theory, you can also put the fixed provider on the master and let it
> sync to your clients via pluginsync:
>  http://docs.puppetlabs.com/guides/plugins_in_modules.html
>
> Else wait until the next Puppet 2.7.9 release in Jan(?) where this
> should be merged, or until Augeas 1.0.0 when the problem will go away.
> Puppet 2.6.x probably won't be fixed unless there's a security release.
>
> Cheers,
>
> --
> Dominic Cleal
> Red Hat Consulting
> m: +44 (0)7817 878113
>
> _______________________________________________
> augeas-devel mailing list
> augeas-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/augeas-devel