"rake puppet:import:puppet_classes" not detecting changes properly
Example how to reproduce it:
Copy a module (mysql for ex.) from another environment (master) to the "production" env:
cp -a /etc/puppet/environments/master/modules/mysql ./mysql
Try running the rake task:
rake puppet:import:puppet_classes RAILS_ENV=production
(in /usr/share/foreman) Evaluating possible changes to your installation No changes detected
And in foreman we don't get the module available in the production environment .
The web interface also doesn't see the change
( https://foreman.test.bluedome.local/puppetclasses/import_environments )
#1 Updated by Marcello de Sousa over 10 years ago
I noticed that, if I "destroy" in foreman a class or an environment and run the rake task again, it then detect and import the changes described above but it won't report them:
1- destroy a class via GUI
2- rake puppet:import:puppet_classes RAILS_ENV=production
Evaluating possible changes to your installation Scheduled changes to your environment New environments : Obsolete environments : New puppetclasses : apache2 Obsolete puppetclasses :
3- "apache2" is re-inported as well as the new "mysql" module/classes (not reported)
#10 Updated by Paul Kelly over 10 years ago
rebased, retested and pushed.
Maybe these minor mods have fixed the issue but I think not.
Ohad if you can reproduce your eval failures I would like to look at your logs :-) I have repeatedly added the example42 database, in various ways, and have had no problems.