Issue #20123 has been updated by Eman Salah.

Status changed from Needs More Information to In Topic Branch Pending Review
Assignee set to Josh Cooper
Target version set to 3.x

Yes Tom that's it!!! Thanks a lot to Josh! 

Me also found 3.1.0 gem installed, I tried to do a fresh Install on another 64 
bit CentOS VM and it worked for me.

Thanks again Josh 

----------------------------------------
Bug #20123: Error: Could not back up path-to-file: Instance name "md5/..." does 
not match requested key "md5/.......//path-to-file"
https://projects.puppetlabs.com/issues/20123#change-89331

* Author: Eman Salah
* Status: In Topic Branch Pending Review
* Priority: Normal
* Assignee: Josh Cooper
* 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