[Puppet Users] Puppet Augeas update/insert Multi line

Before I begin, Please pardon me as I am new to Puppet/Augeas. I am trying to update/insert a word to the existing line. When I use the augtool with the Properties lens, the line value is showing as < multi >. When I parse the line with augparse the result is shown as below. Please help me her

Re: [Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

Hi Fabrice, you can simply copy sudoers.aug from upstream to affected systems with a file resource until augeas 1.9.0 is released. I am not aware though that there are plans to rebase augeas for the 1.x series of puppet-agent

Re: [Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

Looking at Puppet 1.10.8, I see in /opt/puppetlabs/puppet/lib/pkgconfig/augeas.pc: Version: 1.4.0 That version was released on june 2015/ But at https://github.com/hercules-team/augeas/releases, current augeas version is 1.8.1, and still don't include patch for that bug. It prevent upgrade to

Re: [Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

Thanks ! > Le 27 août 2017 à 06:56, David Lutterkort a écrit : > > Hi Fabrice, > > I just merged this change > > to the sudoers lens to address that. You can just overwrite the stock lens > in /usr/shar

[Puppet Users] puppet augeas fails with sudoers in RHEL 7.4

I've upgraded a test machin with Centos 7.4 CR When I run puppet on it, configuring /etc/sudoers with augeas, I'm getting: Warning: Augeas[sudoers include](provider=augeas): Loading failed for one or more files, see debug for /augeas//error output augtool ls /augeas//error says : pos = 2308 lin

[Puppet Users] Puppet Augeas Provider and augtool

Hi, i'm currently developing some manifests using the augeas provider ( mostly using the sudoers lens) and I am permanently running into trouble. It seems that the augeas provider and augtool behave differently regarding path declarations, making it worse to test and develop things. But perhaps

[Puppet Users] Puppet+Augeas sudoers problem

Hi, i'm currently having trouble with augeas. A snipplet which worked fine on my homebox ( ubuntu, some 3.+ puppet, some weeks old... ) does not work on a RHEL6 /Puppet 3.7.4/augeas 1.0 installation: basically, i want to modify the sudoers file with augeas. using augtool this works fine, so i'd

[Puppet Users] puppet augeas is appying twice everytime

Hi I have a problem , I've tried everything but I can't resolve it yet, every time that I run puppet agent it is applying my augeas resources twice basically I have this array in hiera: augeas_views: - 'defnode user hudson/views/au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipeline

[Puppet Users] puppet augeas inittab whitespaces and single/double quotes, backslash

Hi everyone. I am attempting to add this line to /etc/inittab: TS0:23:respawn:/sbin/mgetty -m '"" \d\dAT OK' ttyS0 Here is the puppet manifest I am trying to make: augeas {"/etc/inittab": context => "/files/etc/inittab", changes => [ "set TS0/runlevels 23", "s

Re: [Puppet Users] puppet & augeas - where to put augeas definition?

Hey Pete, Thanks for the info. I think adding a class and "futureproofing" for things like dependencies is probably the way to go, in this specific scenario. Many thanks for the link and for the great information below. I owe you a beer. Cheers, Mike On Thursday, January 23, 2014 12:29

Re: [Puppet Users] puppet & augeas - where to put augeas definition?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi > Per the snippet above, I'm simply trying to add in an extra entry > into my /etc/apt/sources.list but I'm not sure where I would > actually put the above piece of code. I currently have it sitting > in my init.pp file for the corresponding class

[Puppet Users] puppet & augeas - where to put augeas definition?

Hello all, I'm looking to use a simple augeas definition per the below info: augeas { "sources_config": context => "/files/etc/apt/sources.list" , changes => [ "set deb http://repo/ client main" , ], } Per the snipp

[Puppet Users] puppet augeas with more than one array in a single key

I am trying to put together a set of puppet policies for grub/menu.lst. The serial::grubmenulst looks like this : define serial::grubmenulst ( $value ) { $key = $title $context = "/files/boot/grub/menu.lst" augeas { "grubmenulst/${key}": context => "$context",

Re: [Puppet Users] Puppet & Augeas

On 06/06/11 10:01, Kris Buytaert wrote: > To actual errors "change from need_to_run to 0 failed: Save failed with > return code false" when trying to experiment with a syntax like below. > ... > augeas{"sipxprofile" : > lens=> "Xml", > incl=> > "/etc/sipxpbx/freeswitch/conf

[Puppet Users] Puppet & Augeas

I`m struggling with getting puppet to do do an agueas run correctly. When I make the modifications using augtool on the cli Everything works like expected . augtool --noload augtool> set /augeas/load/Xml/incl[last()+1] /etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml augtool> loa

[Puppet Users] Puppet + Augeas + dhcpd.conf

Has anyone used augeas to manage the dhcpd.conf file? I really don't want to have a series of .d directories to build this thing. Each subnet needs to be a resource and each static host entry inside the subnet needs to be its own resource. --~--~-~--~~~---~--~-

[Puppet Users] puppet+augeas inittab

Hi guys, I was enlightened by the 'puppet+augeas modprobe.conf' post (thanks!) and was going to put inittab under puppet/augeas management. My goal is to add this one line for spawning a console on the serial port if it doesn't exist: co:12345:respawn:/sbin/agetty ttyS0 19200 vt100 However the

[Puppet Users] puppet+augeas modprobe.conf

I need to be able to add: alias usb-storage off to /etc/modprobe.conf I have this so far: augeas { "usb-storage": context => "/files/etc/modprobe.conf", changes => [ "set alias[last()+1] usb-storage", "set alias[last()]/modulename off", ], onlyif =>

[Puppet Users] puppet + augeas /etc/exports/dir[*] lookup possible?

I'm not sure if I'm kicking tyres again, but first off: I like the possibilities with puppet + augeas. Trying to make a working example with /etc/exports but not sure of how to proceed. I want to be able to define exports in the following form: my_exports_def { ['/home/server01', '/svr/logs']:

[Puppet Users] Puppet Augeas Plugin

resending, not sure the original made it to the mailing list. Bryan -- I'm using the puppet augeas plugin at http://git.et.redhat.com/?p=ace.git;a=blob;f=modules/augeas/plugins/puppet/type/augeas.rb;h=2346c37d724d7607ed4e09b0413700bec2b7cbed;hb=HEAD I'm running into a behavior that I wouldn't exp

[Puppet Users] Puppet Augeas Plugin

Bryan -- I'm using the puppet augeas plugin at http://git.et.redhat.com/?p=ace.git;a=blob;f=modules/augeas/plugins/puppet/type/augeas.rb;h=2346c37d724d7607ed4e09b0413700bec2b7cbed;hb=HEAD I'm running into a behavior that I wouldn't expect. I'd like to confirm an entry in sysctl.conf by changing t