Issue #20123 has been updated by Josh Cooper.

Subject changed from Error: Could not back up path-to-file: Instance name 
"md5/..." does not match requested key "md5/.......//path-to-file" to Warn if 
multiple versions of puppet are installed
Status changed from In Topic Branch Pending Review to Accepted
Assignee deleted (Josh Cooper)

Tom De Vylder wrote:
> I'm still not quite sure why running the packaged puppet binary would get 
> interfered by installed gems when running the agent manually. I 
> double-checked $PATH, --version, facter and ran which puppet.
> Could this have something to do with recent changes related to loading 
> modules from gem paths?

Yes, puppet's autoloader was modified in 3.0 for (#7788) to load code from 
gems. Since the autoloader is used to load terminii, we see this behavior. The 
code loading was improved in 3.1 (#7316) so that it actually loaded code 
consistently, e.g. for custom faces. But we could probably do a better job of 
warning if there are multiple puppet installs in the resulting `LOAD_PATH`. 
I've updated the bug accordingly.

----------------------------------------
Bug #20123: Warn if multiple versions of puppet are installed
https://projects.puppetlabs.com/issues/20123#change-89375

* Author: Eman Salah
* Status: Accepted
* Priority: Normal
* Assignee: 
* Category: error reporting
* Target version: 3.x
* Affected Puppet version: 3.1.1
* Keywords: 
* Branch: 
----------------------------------------
Operating System: CentOS 6.3 (Virtual machine on VirtualBox Ubuntu Desktop)
Puppet Version: 3.1.1
Ruby Version:  1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Gem Version: 1.8.10

I'm running currently the Puppet Master and client on the same Machine for 
testing Purposes, every time I try the filebucket backup command: "puppet 
filebucket backup path-to-file" I get the following error:
Error: Could not back up path-to-file: Instance name "md5/..." does not match 
requested key "md5/.......//path-to-file"

===> Note I tried downgrading to puppet 2.7.19 on an Identical VM having the 
same problem and everything worked OK

Please Advice 





-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to