Issue #3712 has been updated by Joe McDonagh. Status changed from Needs more information to Rejected
I'm changing this to rejected since Ubuntu 10.04's official canonical nagios3 package *does not* have any parse errors/corruption on files written by naginator. There had to have been some kind of weird library mismatch in my original compile of the custom nagios3 package (ubuntu 8,04 only came with 2, i needed 3). I appreciate the attention to this bug as it was causing some serious head issues while I tracked it down, but it looks really like it just had to with the custom compile of nagios. Maybe if PL encounters this with a customer in the future (weird nagios parse errors) you can make sure it isn't custom-compiled/backported. ---------------------------------------- Bug #3712: Nagios type introducing some kind of corruption to .cfg files http://projects.puppetlabs.com/issues/3712 Author: Joe McDonagh Status: Rejected Priority: Normal Assigned to: Category: nagios Target version: Affected version: 0.25.4 Keywords: Branch: I am seeing that naginator somehow writes files that fail to parse with nagios, but only sometimes. The files visually look fine, but fail with this error: Error: Host '' specified in host group 'ad-servers' is not defined anywhere! Except that there is no host specific in this hostgroup (allowed in at least my version of nagios): # HEADER: This file was autogenerated at Mon May 03 13:00:18 -0400 2010 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. define hostgroup { hostgroup_name ad-servers alias Active Directory Servers } Now, the interesting part is that the error is different on .25.4. I have first tried to do an automatic nagios setup on .24.8 and would get similar errors, but the hostname would be a bunch of garbage characters. If I remove this file as well as a couple more, it eventually quits failing to parse, so not all files are written badly. It is also worth noting that the corruption goes alphabetically. Sounds stupid, but ad-servers.cfg is the first hostgroup alphabetically. Next is aptproxy-servers, which also fails, a couple more, then domino-servers is the last hostgroup that fails to parse. esxi-servers and onwards (alphabetically) give no errors. I am not so sure how to pursue this issue, please let me know whatever information you need to help narrow this down. I can reproduce this with ease. Just rm [a,b,c,d]* in the hostgroups folder, everything parses. Re run puppet to replace the .cfg files, then the error comes back. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
