-- Sent from my HP Veer


On May 24, 2012 17:21, Jeff McCune <j...@puppetlabs.com> wrote:

On Tue, May 22, 2012 at 6:58 AM, Shiva <shivaraman.ramad...@gmail.com> wrote:
I am installing puppet enterprise manager (master) on a RHEL box.
Though the install itself succeeds without any issues, the first run
of puppet when it tries to deploy the pe_mcollective module fails with
the following error.

Message:
change from notrun to 0 failed: sh -c 'umask 077; keytool -
importkeystore -deststorepass puppet -destkeypass puppet -destkeystore
broker.ks -srckeystore broker.p12 -srcstorepass puppet -srcstoretype
PKCS12 -alias puppet-master.xyz.com' returned 1 instead of one of [0]
at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/posix.pp:
138

OK, I dove into this and I think it might be caused by a difference in behavior between Java on CentOS and Java on RHEL.  The keytool command Puppet is executing returns 0 on CentOS 6.2 but this doesn't guarantee the behavior is the same with RHEL 6.2.

Could you let me know what /usr/bin/keytool is using ls -l?  If it's a symbolic link, can you follow it and let me know where it ends up?  Finally, could you run rpm -qf on the resulting file?  (for me on CentOS 6.2 it ultimately links to /usr/lib/jvm/jre-1.6.0-openjdk/bin/keytool owned by java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686
 
-Jeff

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Reply via email to