It really depends. The "chef way" to do that, is to make sure you add the
"chef-client" recipe when you bootstrap the node for the first time. This
way it will keep in sync with the Chef Server.
At this point, you don't have to access the node anymore. You just have to
use the ChefApi to get the n
Hi Ignasi,
Passing ssl ca to chef node while doing first bootstrap actually worked for
me. Some issue was there regarding the certificate. Thanks a lot for your
suggestion.
One thing though, after bootstrapping to install chef-client If I want to
bootstrap again with a particular recipe present i
Then the problem is just about the Chef configuration and with the
certificate itself. Are you sure it is the right one?
I'd recommend you to read the Chef client config documentation [1],
especially the "ssl_*" properties. Play with them. You'll see that despite
not being the recommended solution
Hi Ignasi,
The certificate is generating now in chef client side, but still the SSl
authentication is failing. Please let me know how to proceed.
Thank you for installing Chef!
[2015-02-12T08:59:31+00:00] INFO: Forking chef instance to converge...
[2015-02-12T08:59:31+00:00] INFO: *** Chef 12.0.3
Sorry... same mail fired many times from my end, some issue with gmail.
Cant delete from the mailing list also :$
Regards,
Subhadip
---
On Thu, Feb 12, 2015 at 9:12 AM, Subhadip Bagui
Hi Ignasi,
I tried the code u suggested. I'm getting some error now like that crt file
what we have passed cannot be created in chef client. Please suggest.
[2015-02-11T18:18:32+00:00] INFO: Client key /etc/chef/client.pem is not
present - registering
^[[0m
===
Hi Ignasi,
I tried the code u suggested. I'm getting some error now like that crt file
what we have passed cannot be created in chef client. Please suggest.
[2015-02-11T18:18:32+00:00] INFO: Client key /etc/chef/client.pem is not
present - registering
^[[0m
===
Hi Ignasi,
I tried the code u suggested. I'm getting some error now like that crt file
what we have passed cannot be created in chef client. Please suggest.
[2015-02-11T18:18:32+00:00] INFO: Client key /etc/chef/client.pem is not
present - registering
^[[0m
===
Hi Ignasi,
I tried the code u suggested. I'm getting some error now like that crt file
what we have passed cannot be created in chef client. Please suggest.
[2015-02-11T18:18:32+00:00] INFO: Client key /etc/chef/client.pem is not
present - registering
^[[0m
===
Hi Ignasi,
I tried the code u suggested. I'm getting some error now like that file
what we have passed cannot be created in chef client. Please suggest.
[2015-02-11T18:18:32+00:00] INFO: Client key /etc/chef/client.pem is not
present - registering
^[[0m
===
Ok, you're hitting JCLOUDS-792 [1]. It is fixed in the latest snapshot.
Basically, the Chef client 12 comes with SSL verification enabled by
default, and since the node you deployed does not trust the Chef Server's
certificate, it aborts.
If you can't upgrade to the latest snapshot, then you can
Hi Ignasi,
I checked in the stdout.log that is generating in /tmp/jclouds-script.../
and its showing the below error.. Attaching the full log also. Any idea how
to fix this.
[2015-02-08T17:41:25+00:00] INFO: Chef-client pid: 7023
*[2015-02-08T17:41:28+00:00] INFO: Client key /etc/chef/client.pem
Hi,
I've added the properties for customized chef as below.
chefConfig.put(ChefProperties.CHEF_USE_OMNIBUS, false);
chefConfig.put(ChefProperties.CHEF_VERSION,"11.16.4");
But now it seems chef is not able to download from opscode and install the
rpm. I waited for 1/2 hr and no files are getting d
The Chef version properties will only work if you install Chef
directly from the Chef gems. Support or versions when using omnibus
was added in the latest snapshot so it is not available in 1.7.3.
You can instruct jclouds to install Chef directly from the Chef gems
by configuring the Chef properti
Hi Ignasi,
Changing the JClouds version will be difficult for me as the code is there
in production. I will check with changing the chef version properties and
let u know.
Regards,
Subhadip
-
The configuration seems correct. Can you try using version
2.0.0-SNAPSHOT and set the chef version I suggested, and see if it
works? Just to isolate the issue and see if it is actually a package
version.
On 9 February 2015 at 11:43, Subhadip Bagui wrote:
> Hi Ignasi,
>
> Thanks for your reply.
>
Hi Ignasi,
Thanks for your reply.
I'm using jclouds version 1.7.3 and I'm not setting any chef version in
code. Default it's taking that opscode-omnibus chef.
I have cleaned the /var/chef dir and tried but getting the same issue.
Here is my code for ChefService creation. Please let me know what
Could you also share the code you use to create the ChefContext? Just
to make sure the credentials and validator certificates are properly
configured. Thanks!
On 9 February 2015 at 09:18, Ignasi Barrera wrote:
> It seems to be failing to install the Chef RPM (and that would be an
> issue with the
It seems to be failing to install the Chef RPM (and that would be an
issue with the Chef package itself). To debug what is going on, you
can:
* Log in to the node after the script execution failure.
* Remove the "/etc/chef" directory, to cleanup everything jclouds has
created there.
* In the user'
19 matches
Mail list logo
