Hi everyone, I'm faced a really strange issue that I never saw before. I manage a complete infrastructure (~300 nodes, ~100.000 resources) using Puppet and this is the only case I saw behaving this way.
1. I have my own bacula module (class bacula). 2. I have a machine, with "bacula" as its hostname. With this hostname, bacula class is loaded (mco inventory shows it), but if I change anything in the module, added any new resource (I tried even generate a test file at the beggining of the init.pp), is not applied. 3. If I change the name to any other name, like bacula2, bacula-01, whatever, (clean & deactivate node, re-generate SSL certs, etc.) it works fine. Of course, if I change it back again to "bacula", it's not changing anything again :-S. Tests I did: - Check puppetserver logs - Check puppet agent -t --debug --evaltrace (nothing about "bacula" class) - Reinstalling the machine from scratch - Using another totally different machine (physical & virtual), setting its hostname to "bacula". Same happens (so it's not related to that specific machine). - Re-develop the module. Same happens. It only happens when 'bacula' is the name of the module/class, and 'bacula' is the hostname of the machine >.< Any idea about how to debug this rare issue? Versions used: - puppetserver version: 2.7.2 - puppet agent version: 4.8.2 (tested also with 4.10.1) Thanks in advance. Best regards, Abel. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b54cd756-23a9-4238-8645-d73d31fa1607%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
