Actions
Bug #565
closed"rake puppet:import:puppet_classes" not detecting changes properly
Description
Example how to reproduce it:
PuppetEnvironment:
[production] modulepath=/etc/puppet/environments/production/modules
Copy a module (mysql for ex.) from another environment (master) to the "production" env:
cd /etc/puppet/environments/production/modules
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 )
Updated by Paul Kelly over 14 years ago
- Status changed from New to Ready For Testing
- Assignee changed from Ohad Levy to Paul Kelly
- Branch set to bug/565-import-puppet_classes-wrong
Updated by Paul Kelly about 14 years ago
- Status changed from Ready For Testing to Need more information
Updated by Paul Kelly about 14 years ago
- Status changed from Need more information to Ready For Testing
- % Done changed from 0 to 100
Actions