Bug #565
closed
"rake puppet:import:puppet_classes" not detecting changes properly
Added by Marcello de Sousa over 13 years ago.
Updated about 13 years ago.
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 )
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)
- 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
Just rewrote the whole thing.
- Status changed from Ready For Testing to Closed
- Status changed from Closed to Ready For Testing
oops, closed by mistake, reopening
- Status changed from Ready For Testing to Need more information
Ohad, You say that you experienced some problems with this patch. Something about an eval that failed. Could you provide more information? Maybe the log showing the http call?
Hi, I've installed today the latest Foreman from the develop branch and still having similar problems as in the description of this issue.
It still doesn't detect changes properly with both the script and the Web interface.
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.
- Status changed from Need more information to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by