Issue #17486 has been updated by Jo Rhett.

So on our systems we apparently have a dozen or so files not managed by puppet 
that augeas don't like. These files are not fixable in any immediate sense -- 
they require a code update, qa cycle, etc to repair.  There's nothing wrong 
with the files, but augeas has complaints.

This used to be silent or low-level notice. I don't feel that putting this at 
warning level (above notice) is the appropriate answer.
----------------------------------------
Bug #17486: Augeas provider warns on parse errors in other files handled by 
same lens
https://projects.puppetlabs.com/issues/17486#change-82643

Author: Linux Bami
Status: Accepted
Priority: Low
Assignee: 
Category: augeas
Target version: 3.x
Affected Puppet version: 3.0.1
Keywords: augeas, provider
Branch: 


Greetings,

we are evaluating Puppet 3.0. At the moment we are getting errors from the 
augeas provider:
Warning: Augeas[xxxxxx](provider=augeas): Loading failed for one or more files, 
see debug for /augeas//error output

$ rpm -qa|grep puppet
puppet-server-3.0.1-1.el6.noarch
puppet-3.0.1-1.el6.noarch
puppetdb-terminus-1.0.2-1.el6.noarch
puppet-dashboard-1.2.12-1.el6.noarch
$ rpm -qa|grep augeas
augeas-libs-0.9.0-1.el6.x86_64
augeas-0.9.0-1.el6.x86_64
augeas-devel-0.9.0-1.el6.x86_64
ruby-augeas-0.4.1-1.el6.x86_64

The file manipulation of the files via augtool and the provider works fine but 
we always get the warning.

Same modules works fine with puppet 2.7 without any warnings



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to