This may or may not be the right place to ask this, but I''m sure it''ll lead me there. I''m using Puppet packages from EPEL (thanks to whoever provides these). I pushed out some new configs that use Augeas to make changes and they threw errors on most of my servers. Installing the "augeas" package made puppetd happy. (ruby-augeas and augeas-libs had already been pulled in when I installed puppet.) I was thinking the puppet package should list the augeas package as a dependency, but perhaps the ruby-augeas package can''t function without it in any context, in which case the dependency should be there. If anyone knows, I''ll try to contact the appropriate package maintainer to let them know (assuming they aren''t already reading this). Thanks. -- Rob McBroom <http://www.skurfer.com/> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Rob McBroom wrote:> This may or may not be the right place to ask this, but I''m sure > it''ll lead me there. > > I''m using Puppet packages from EPEL (thanks to whoever provides > these).Heh, the hard work is writing puppet. Packaging it is relatively simple.> I pushed out some new configs that use Augeas to make changes and > they threw errors on most of my servers. Installing the "augeas" > package made puppetd happy. (ruby-augeas and augeas-libs had already > been pulled in when I installed puppet.)What did the manifests look like? What were the errors? And what versions of puppet, augeas, and ruby-augeas? :) I have epel-testing enabled and these versions: augeas-libs-0.5.0-2.el5 puppet-0.25.0-0.1.beta1.el5 ruby-augeas-0.2.0-1.el5 A simple config like this works fine without augeas installed: augeas { ''poppassd'': context => ''/files/etc/xinetd.d/poppassd/poppassd'', changes => [ ''set /disable no'', ''set /bind 127.0.0.1'', ], require => Package[''poppassd''], notify => Service[''xinetd''], }> I was thinking the puppet package should list the augeas package as a > dependency, but perhaps the ruby-augeas package can''t function without > it in any context, in which case the dependency should be there. If > anyone knows, I''ll try to contact the appropriate package maintainer > to let them know (assuming they aren''t already reading this).Most of us probably are. At least, enough of us to help figure out if there is a packaging bug and who to point the finger at for a fix. ;) -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ How much does it cost to entice a dope-smoking UNIX system guru to Dayton? -- Brian Boyle, UNIX/WORLD''s First Annual Salary Survey
On Wed, May 27, 2009 at 9:54 AM, Rob McBroom <mailinglist0@skurfer.com> wrote:> > This may or may not be the right place to ask this, but I''m sure it''ll > lead me there. > > I''m using Puppet packages from EPEL (thanks to whoever provides these). > > I pushed out some new configs that use Augeas to make changes and they > threw errors on most of my servers. Installing the "augeas" package > made puppetd happy. (ruby-augeas and augeas-libs had already been > pulled in when I installed puppet.) > > I was thinking the puppet package should list the augeas package as a > dependency, but perhaps the ruby-augeas package can''t function without > it in any context, in which case the dependency should be there. If > anyone knows, I''ll try to contact the appropriate package maintainer > to let them know (assuming they aren''t already reading this). > > Thanks.Rob- The reason augeas is not a dependency is because puppet works just fine without it and a lot of sites do not want or need the extra functions that augeas provides, kind of like the way puppet does not require any particular software provider to be installed. It is an extra function dependency not a core puppet dependency. You can tell puppet to make sure it is installed before you use the augeas features with an augeas default in the main manifest. evan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Evan Hisey wrote:> The reason augeas is not a dependency is because puppet works just > fine without it and a lot of sites do not want or need the extra > functions that augeas provides, kind of like the way puppet does not > require any particular software provider to be installed. It is an > extra function dependency not a core puppet dependency. You can > tell puppet to make sure it is installed before you use the augeas > features with an augeas default in the main manifest.Not exactly true. The puppet packages from EPEL do have a requirement on ruby-augeas. While it is not a hard dependency of puppet, it does provide enhanced functionality that we wanted to ''Just Work'' after installation. (Similarly, we require libselinux-ruby where it is available, which is just Fedora >= 9 for now. RHEL 5.4 will include it as well, when it is released.) I know that some folks don''t like this, and in the future it will be easier to rebuild the EPEL packages without augeas (and selinux) by passing --without augeas and/or --without selinux to rpmbuild or mock. This change is in the current puppet.spec in git (700ad5b). -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Whenever you find yourself on the side of the majority, it is time to pause and reflect. -- Mark Twain
On Wed, May 27, 2009 at 10:10 AM, Todd Zullinger <tmz@pobox.com> wrote:> Evan Hisey wrote: >> The reason augeas is not a dependency is because puppet works just >> fine without it and a lot of sites do not want or need the extra >> functions that augeas provides, kind of like the way puppet does not >> require any particular software provider to be installed. It is an >> extra function dependency not a core puppet dependency. You can >> tell puppet to make sure it is installed before you use the augeas >> features with an augeas default in the main manifest. > > Not exactly true. The puppet packages from EPEL do have a requirement > on ruby-augeas. While it is not a hard dependency of puppet, it does > provide enhanced functionality that we wanted to ''Just Work'' after > installation. (Similarly, we require libselinux-ruby where it is > available, which is just Fedora >= 9 for now. RHEL 5.4 will include > it as well, when it is released.)Hmmm we need to put that on the list of packages that we do not ship then. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 2009-May-27, at 11:24 AM, Todd Zullinger wrote:> What did the manifests look like?This is one that was causing problems. I''m pretty sure the "changes" were already in place, so puppet didn''t need to do anything. augeas { "main.cf": require => Package["postfix"], context => "/files/etc/postfix/main.cf", changes => [ "set canonical_maps ldap:/etc/postfix/addresses.ldap", # "ins #comment before canonical_maps", # "set #comment[.=''''] ''refer to LDAP for To and From address''", "set mydomain blah.com", "set relayhost [smtp.blah.com]", ], notify => Service["postfix"], }> What were the errors?I removed augeas in an attempt to reproduce this error, but it doesn''t fail any more, so perhaps it''s something about the augeas package''s installation process and not the presence of augeas itself? Anyway, I was able to find an example of the error in yesterday''s logs. May 26 16:36:35 t-corp-scmvm-0a puppetd[21954]: (//mta/ Augeas[main.cf]/returns) change from need_to_run to 0 failed: Save failed with return code false And I swear the sequence was only this: % service puppet stop % puppetd --test typical stuff plus the error above % yum install augeas % puppetd --test works this time So, you can see why I would think it was requiring augeas, but maybe there''s more to it.> And what versions of puppet, augeas, and ruby-augeas? :)puppet-0.24.8-1.el5.1 ruby-augeas-0.2.0-1.el5 augeas-libs-0.5.0-2.el5 augeas-0.5.0-2.el5 (Augeas is installed now, but wasn''t when the error occurred.)> A simple config like this works fine without augeas installed:It''s not installed now, or it was never installed? Thanks. -- Rob McBroom <http://www.skurfer.com/> Because it screws up the order in which people normally read text. Original message:> Why is it bad to top-post your reply?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Rob McBroom wrote:> This is one that was causing problems. I''m pretty sure the "changes" > were already in place, so puppet didn''t need to do anything. > > augeas { "main.cf": > require => Package["postfix"], > context => "/files/etc/postfix/main.cf", > changes => [ > "set canonical_maps ldap:/etc/postfix/addresses.ldap", > # "ins #comment before canonical_maps", > # "set #comment[.=''''] ''refer to LDAP for To and From address''", > "set mydomain blah.com", > "set relayhost [smtp.blah.com]", > ], > notify => Service["postfix"], > }That looks sane enough at a glance (and to a non-augeas guru).>> What were the errors? > > I removed augeas in an attempt to reproduce this error, but it doesn''t > fail any more, so perhaps it''s something about the augeas package''s > installation process and not the presence of augeas itself?I can''t imagine what that might be though. There aren''t any scripts or triggers in the augeas* or ruby-augeas packages. Not that I''m trying to rule out the unexplained. :)> Anyway, I was able to find an example of the error in yesterday''s > logs. > > May 26 16:36:35 t-corp-scmvm-0a puppetd[21954]: (//mta/ > Augeas[main.cf]/returns) change from need_to_run to 0 failed: Save > failed with return code falseHopefully some of the more augeas-aware folks can chime in if that''s a common error with a known cause.> And I swear the sequence was only this: > > % service puppet stop > % puppetd --test > typical stuff plus the error above > % yum install augeas > % puppetd --test > works this time > > So, you can see why I would think it was requiring augeas, but maybe > there''s more to it.Indeed. That would peak my curiosity too.>> And what versions of puppet, augeas, and ruby-augeas? :) > > puppet-0.24.8-1.el5.1 > ruby-augeas-0.2.0-1.el5 > augeas-libs-0.5.0-2.el5 > augeas-0.5.0-2.el5 > > (Augeas is installed now, but wasn''t when the error occurred.) > >> A simple config like this works fine without augeas installed: > > It''s not installed now, or it was never installed?On that particular box, it had been installed before, while I was experimenting with augtool. To test, I added a similar augeas config on a box that I know has never had augeas installed on it. That worked as well. Unfortunately, that seems to rule out the easy packaging bug. :/ Let''s see if David Lutterkort or any of the other augeas folks here have better ideas. If not, and you can reproduce this, a bug report would be in order. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Disobedience: The silver lining to the cloud of servitude. -- Ambrose Bierce
On 2009-May-27, at 2:27 PM, Todd Zullinger wrote:> I can''t imagine what that might be though. There aren''t any scripts > or triggers in the augeas* or ruby-augeas packages. Not that I''m > trying to rule out the unexplained. :)Yes, since it''s not as reproducible as I thought, I meant to add that I''ll try to reproduce it on a other system and share the results. I have several that have never been touched by EPEL, Puppet or Augeas, but there are many layers of red tape around changing these systems which is why they''ve never been touched by… well, you get the idea. There are a couple of new systems that are supposedly getting cabled up tomorrow. If that goes as expected, I''ll get on and mess with them before anyone knows they''re there. -- Rob McBroom <http://www.skurfer.com/> Because it screws up the order in which people normally read text. Original message:> Why is it bad to top-post your reply?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On 2009-May-27, at 3:35 PM, Rob McBroom wrote:> There are a couple of new systems that are supposedly getting cabled > up tomorrow. If that goes as expected, I''ll get on and mess with them > before anyone knows they''re thereIt took our network team until today to sort out the firewall rules so I could get to these boxes. They seem to function just fine having never had the augeas package installed, so it seems I can''t reproduce it. the only notable difference is that these new servers are physical, while I noticed the problem on VMs. Seems unlikely to matter, but if I get a chance to test it on a VM, I will. -- Rob McBroom <http://www.skurfer.com/> Because it screws up the order in which people normally read text. Original message:> Why is it bad to top-post your reply?--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---