Hi Susanta, There was an issue related to a similar error that was resolved in agent version 4.6.5, but it appears that you are using version 4.9.2 so this should not impact you.
This may be related to the self-signed certificate. Scalr uses the Chef defaults for ssl_verify_peer. In Chef 11 default value is "none", but in Chef 12 the default is "verify". Either of the following should mitigate this: 1. Use authoritative SSL cert for your Chef server. 2. On the Chef bootstrap tab for the Role, select SSL verify mode "NONE". More information is available in our documentation here <https://scalr-wiki.atlassian.net/wiki/display/docs/Chef+Configuration+in+the+Role+Scope>. Please let us know if this resolves the problem for you. Many thanks, Wm. Marc O'Brien Scalr Technical Support On Thursday, July 28, 2016 at 7:05:13 PM UTC-6, Susant Padhi wrote: > > Marc and Team, > > I am using the scalr community edition 5.22 and chef 12.8. I have created > my AMI with chef and created a ROLE including chef. > But it never able to bootstrap always failing with "[SSL: > CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)" > > I have tried providing the clientele template too with different > option.but no luck > chef_server_url "https://XXXXXXXXXXX/myORG"; > ssl_verify_mode :verify_none > > 2. Then created a AMI with chef server certificate and then provided > following options. > chef_server_url "https://XXXXXXXXXXX/myORG"; > trusted_certs_dir "/etc/chef/trusted_certs" > > Would appreciate a quick respond/help on it. > > > Best Regards > > Susanta > > > > > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
