Thanks for your reply. Unfortunately that isn’t a workable solution in my environment. I’m hoping I can get a clean solution to setting the environment during the bootstrap, but in the meantime I’m working around it by writing a little shell wrapper for the bootstrap commands, which bootstraps with an empty runlist, then uses knife to set the run list, then uses knife exec to set then environment, and finally knife ssh to run chef-client. From:
[mailto:
On Behalf Of Michael Herman
Sent: Monday, September 12, 2011 5:35 PM
To:
Subject: [chef] Re: RE: Re: RE: Unable to set environment on a node during bootstrap I ran into the same issue. I worked around it by including an "environment" statement in the bootstrapped client.rb file. The problem with this is that changing the environment then becomes a change in the file, rather than via knife, though not a problem in my location. mgh On Tue, Sep 13, 2011 at 6:03 AM, Michael Garrett <
">
> wrote: 0.10.2 on the workstation also.
-----Original Message-----
From: Noah Kantrowitz [mailto:
">
]
Sent: Monday, September 12, 2011 3:36 PM
To:
">
Subject: [chef] Re: RE: Unable to set environment on a node during
bootstrap
What version of Chef is installed on your workstation?
--Noah
On Sep 12, 2011, at 12:19 PM, Michael Garrett wrote:
> Forgot to note that I'm using chef server 0.10.2.
>
> -----Original Message-----
> From:
">
[mailto:
">
]
> Sent: Monday, September 12, 2011 12:04 PM
> To:
">
> Subject: [chef] Unable to set environment on a node during bootstrap
>
>
> Hello all,
>
> I'm trying to bootstrap a new node, and set its environment so the
> correct
> versions of its cookbooks are run during the bootstrap process. It
> doesn't
> seem to work - the new node is created with the environment
"_default".
> Here's
> the bootstrap command I'm using:
>
> knife bootstrap node.domain -N node.domain -x root -P XXXXXX -r
> role[datacenter1],role[dev],recipe[baseline] --distro centos5-gems
> --environment dev
>
> thanks in advance.
>
> -mg
>
> ***CONFIDENTIALITY NOTICE and DISCLAIMER***
> This message and any attachment are confidential and may be
> privileged or otherwise protected from disclosure and solely for
> the use of the person(s) or entity to whom it is intended. If you
> have received this message in error and are not the intended
> recipient, please notify the sender immediately and delete this
> message and any attachment from your system. If you are not the
> intended recipient, be advised that any use of this message is
> prohibited and may be unlawful, and you must not copy this
> message or attachment or disclose the contents to any other person.
***CONFIDENTIALITY NOTICE and DISCLAIMER***
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.
***CONFIDENTIALITY NOTICE and DISCLAIMER***
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.
|