Hosted chef not honoring passed environment?

Darron_Froese · January 10, 2013, 9:25pm

Using chef 10.16.4.

I have an environment called ‘lucid’ for my current infrastructure:

[master] darron@~/Dropbox/src/chef-repo: knife environment list
_default
lucid

We’re using hosted Chef and this next bit shows all of my cookbook
versions for that environment:

gist.github.com

https://gist.github.com/darron/4505868

gistfile1.txt

[master] darron@~/Dropbox/src/chef-repo: knife environment show lucid
chef_type:            environment
cookbook_versions:   
  apache2:                    0.99.23
  apache2_mod_security:       0.24.0
  apt:                        1.1.2
  apt-no-cache:               0.0.3
  apt_get_update:             0.0.3
  apt_get_update_upgrade:     0.0.6
  apt_vagrant:                0.8.0

This file has been truncated. show original

I’m adding a new server using that environment - tried passing
environment along 2 different ways:

bundle exec knife rackspace server create -E lucid -S server2013 -f 4
-N server2013 --image 112 -r
’role[setup],role[mysql_server],role[web_server],recipe[backup]’
–distro ubuntu10.04-ruby193

OR

bundle exec knife rackspace server create -S server2013 -f 4 -N
server2013 --image 112 -r
’role[setup],role[mysql_server],role[web_server],recipe[backup]’
–distro ubuntu10.04-ruby193 --environment lucid

Neither seems to work as I expect.

The server gets created, but at the end of the run, it says:

Name: server2013
Flavor: 2GB server
Image: Ubuntu 10.04 LTS
Metadata: {}
Environment: lucid
Run List: role[setup], role[mysql_server], role[web_server], recipe[backup]

But:

It uses the 2.0.4 sudo cookbook that I uploaded yesterday - which
is not part of the lucid environment.
In the Opscode management interface it shows up as _default:
http://d.pr/i/UoZz

Any ideas what I’m missing?

Darron_Froese · January 14, 2013, 6:33am

Tried again a few different times this weekend - same failures -
downloading the wrong version of the sudo cookbook and being assigned
to the wrong environment:

bundle exec knife rackspace server create -E lucid -S sudo2013 -f 2 -N
sudo2013 --image 112 -r 'recipe[sudo]' --distro ubuntu10.04-ruby187

gist.github.com

https://gist.github.com/darron/4527988

gistfile1.sh

[master] darron@~/Dropbox/src/chef-repo: bundle exec knife rackspace server create -E lucid -S sudo2013 -f 2 -N sudo2013 --image 112 -r 'recipe[sudo]' --distro ubuntu10.04-ruby187
Instance ID: 21350887
Host ID: ae0271c772ca67f3f3ac2ca4e367991f
Name: sudo2013
Flavor: 512 server
Image: Ubuntu 10.04 LTS
Metadata: {}

Waiting server................................................................................................
Public DNS Name: 184-106-71-147.static.cloud-ips.com

This file has been truncated. show original

http://d.pr/i/rjBp

bundle exec knife bootstrap -E lucid -r "recipe[sudo]" 184.106.71.194
-x root -P not-so-fast --node-name bootstrap2013 --distro
ubuntu10.04-ruby187

gist.github.com

https://gist.github.com/darron/4528030

gistfile1.txt

[master] darron@~/Dropbox/src/chef-repo: bundle exec knife bootstrap -E lucid -r "recipe[sudo]" 184.106.71.194 -x root -P yeah-sure-ha-ha --node-name bootstrap2013 --distro ubuntu10.04-ruby187
Bootstrapping Chef on 184.106.71.194
0% [Working]94 
Get:1 http://security.ubuntu.com lucid-security Release.gpg [198B]
Hit http://archive.ubuntu.com lucid Release.gpg    
Get:2 http://archive.ubuntu.com lucid-updates Release.gpg [198B]
99% [Waiting for headers]                           
Hit http://archive.ubuntu.com lucid Release
Get:3 http://security.ubuntu.com lucid-security Release [57.3kB]
10% [Release gpgv 57.2kB] [Waiting for headers] [3 Release 5428B/57.3kB 9%]

This file has been truncated. show original

http://d.pr/i/DBDx

I also tried AWS:

bundle exec knife ec2 server create -E lucid -r "recipe[sudo]" -I
ami-ab36fbc2 -f m1.small -S dfroese -G varnish -x ubuntu --region
us-east-1 -Z us-east-1a --node-name aws2013 --distro
ubuntu10.04-ruby187

gist.github.com

https://gist.github.com/darron/4528155

gistfile1.txt

Last login: Sun Jan 13 23:21:00 on ttys000
[master] darron@~/Dropbox/src/chef-repo: bundle exec knife ec2 server create -E lucid -r "recipe[sudo]" -I ami-ab36fbc2 -f m1.small -S dfroese -G varnish -x ubuntu --region us-east-1 -Z us-east-1a --node-name aws2013 --distro ubuntu10.04-ruby187
Instance ID: i-630f7512
Flavor: m1.small
Image: ami-ab36fbc2
Region: us-east-1
Availability Zone: us-east-1a
Security Groups: varnish
Tags: {"Name"=>"aws2013"}

This file has been truncated. show original

http://d.pr/i/n6Pg

I expect to be able to create new servers and assign them to a
particular environment - is this correct?

Am I misunderstanding something or is something odd going on?

On Thu, Jan 10, 2013 at 2:25 PM, Darron Froese darron@froese.org wrote:

Using chef 10.16.4.

I have an environment called 'lucid' for my current infrastructure:

[master] darron@~/Dropbox/src/chef-repo: knife environment list
_default
lucid

We're using hosted Chef and this next bit shows all of my cookbook
versions for that environment:

gist:4505868 · GitHub

I'm adding a new server using that environment - tried passing
environment along 2 different ways:

bundle exec knife rackspace server create -E lucid -S server2013 -f 4
-N server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193

OR

bundle exec knife rackspace server create -S server2013 -f 4 -N
server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193 --environment lucid

Neither seems to work as I expect.

The server gets created, but at the end of the run, it says:

Name: server2013
Flavor: 2GB server
Image: Ubuntu 10.04 LTS
Metadata: {}
Environment: lucid
Run List: role[setup], role[mysql_server], role[web_server], recipe[backup]

But:

It uses the 2.0.4 sudo cookbook that I uploaded yesterday - which
is not part of the lucid environment.

In the Opscode management interface it shows up as _default:
http://d.pr/i/UoZz

Any ideas what I'm missing?

AJ_Christensen · January 14, 2013, 7:20am

Hey Darron,

It definitely looks like the ec2 server create should be passing through
the environment as you've specified it. [0]

Can you gist the contents of the client.rb as rendered post-bootstrap, when
you notice the machine assigned to the wrong environment, and the full
debug logs, if you haven't already posted those?

Cheers,

AJ

[0]

github.com

chef/knife-ec2/blob/main/lib/chef/knife/ec2_server_create.rb#L343


      
          msg_pair("Volume Tags", printed_volume_tags)
          msg_pair("SSH Key", server.key_name)
          msg_pair("T2/T3 Unlimited", printed_t2_t3_unlimited)
          
          puts("\n")
          
          # occasionally 'ready?' isn't, so retry a couple times if needed.
          tries = 6
          begin
            disable_source_dest_check if vpc_mode? && config[:disable_source_dest_check]
          
            create_tags(hashed_tags) unless hashed_tags.empty?
            create_volume_tags(hashed_volume_tags) unless hashed_volume_tags.empty?
            associate_address(elastic_ip) if config[:associate_eip]
            enable_classic_link(config[:classic_link_vpc_id], config[:classic_link_vpc_security_group_ids]) if config[:classic_link_vpc_id]
          rescue Aws::EC2::Errors::ServiceError, Aws::EC2::Errors::Error
            raise if (tries -= 1) <= 0
          
            ui.warn("server not ready, retrying tag application (retries left: #{tries})")
            sleep 5
            retry

On 14 January 2013 19:33, Darron Froese darron@froese.org wrote:

Tried again a few different times this weekend - same failures -
downloading the wrong version of the sudo cookbook and being assigned
to the wrong environment:

bundle exec knife rackspace server create -E lucid -S sudo2013 -f 2 -N
sudo2013 --image 112 -r 'recipe[sudo]' --distro ubuntu10.04-ruby187

Environment doesn't seem to be working. · GitHub
http://d.pr/i/rjBp

bundle exec knife bootstrap -E lucid -r "recipe[sudo]" 184.106.71.194
-x root -P not-so-fast --node-name bootstrap2013 --distro
ubuntu10.04-ruby187

Tried via regular bootstrap. · GitHub
http://d.pr/i/DBDx

I also tried AWS:

bundle exec knife ec2 server create -E lucid -r "recipe[sudo]" -I
ami-ab36fbc2 -f m1.small -S dfroese -G varnish -x ubuntu --region
us-east-1 -Z us-east-1a --node-name aws2013 --distro
ubuntu10.04-ruby187

AWS · GitHub
http://d.pr/i/n6Pg

I expect to be able to create new servers and assign them to a
particular environment - is this correct?

Am I misunderstanding something or is something odd going on?

On Thu, Jan 10, 2013 at 2:25 PM, Darron Froese darron@froese.org wrote:

Using chef 10.16.4.

I have an environment called 'lucid' for my current infrastructure:

[master] darron@~/Dropbox/src/chef-repo: knife environment list
_default
lucid

We're using hosted Chef and this next bit shows all of my cookbook
versions for that environment:

gist:4505868 · GitHub

I'm adding a new server using that environment - tried passing
environment along 2 different ways:

bundle exec knife rackspace server create -E lucid -S server2013 -f 4
-N server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193

OR

bundle exec knife rackspace server create -S server2013 -f 4 -N
server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193 --environment lucid

Neither seems to work as I expect.

The server gets created, but at the end of the run, it says:

Name: server2013
Flavor: 2GB server
Image: Ubuntu 10.04 LTS
Metadata: {}
Environment: lucid
Run List: role[setup], role[mysql_server], role[web_server],
recipe[backup]

But:

It uses the 2.0.4 sudo cookbook that I uploaded yesterday - which
is not part of the lucid environment.

In the Opscode management interface it shows up as _default:
http://d.pr/i/UoZz

Any ideas what I'm missing?

Darron_Froese · January 14, 2013, 6:19pm

OK - I think I've found a few more clues now - seems that
config_content isn't putting everything it should into the
/etc/chef/client.rb.

This is the command:

bundle exec knife ec2 server create -V -V -E lucid -r "recipe[sudo]"
-I ami-ab36fbc2 -f m1.small -S dfroese -G varnish -x ubuntu --region
us-east-1 -Z us-east-1a --node-name aws2019 --distro
ubuntu10.04-ruby187

The bootstrap has this in it:

(
cat <<'EOP'
<%= config_content %>
EOP
) > /etc/chef/client.rb

and this is the /etc/chef/client.rb:

log_level :info
log_location STDOUT
chef_server_url "Sign In - Chef Manage"
validation_client_name "nonfiction-validator"
node_name "aws2019"

If I manually create the /etc/chef/client.rb in my bootstrap recipe
then it works as I would expect:

(
cat <<'EOP'
log_level :info
log_location STDOUT
chef_server_url "<%= Chef::Config[:chef_server_url] %>"
validation_client_name "<%= Chef::Config[:validation_client_name] %>"
<% if @config[:chef_node_name] == nil %>

Using default node name"

<% else %>
node_name "<%= @config[:chef_node_name] %>"
<% end %>
environment "<%= Chef::Config[:environment] %>"
EOP
) > /etc/chef/client.rb

Will just adjust my bootstraps for the time being - not sure where
else to look now for the actual cause.

Thanks for the tip.

On Mon, Jan 14, 2013 at 12:20 AM, AJ Christensen aj@junglist.gen.nz wrote:

Hey Darron,

It definitely looks like the ec2 server create should be passing through the
environment as you've specified it. [0]

Can you gist the contents of the client.rb as rendered post-bootstrap, when
you notice the machine assigned to the wrong environment, and the full debug
logs, if you haven't already posted those?

Cheers,

AJ

[0]
knife-ec2/lib/chef/knife/ec2_server_create.rb at main · chef/knife-ec2 · GitHub

On 14 January 2013 19:33, Darron Froese darron@froese.org wrote:

Tried again a few different times this weekend - same failures -
downloading the wrong version of the sudo cookbook and being assigned
to the wrong environment:

bundle exec knife rackspace server create -E lucid -S sudo2013 -f 2 -N
sudo2013 --image 112 -r 'recipe[sudo]' --distro ubuntu10.04-ruby187

Environment doesn't seem to be working. · GitHub
http://d.pr/i/rjBp

bundle exec knife bootstrap -E lucid -r "recipe[sudo]" 184.106.71.194
-x root -P not-so-fast --node-name bootstrap2013 --distro
ubuntu10.04-ruby187

Tried via regular bootstrap. · GitHub
http://d.pr/i/DBDx

I also tried AWS:

bundle exec knife ec2 server create -E lucid -r "recipe[sudo]" -I
ami-ab36fbc2 -f m1.small -S dfroese -G varnish -x ubuntu --region
us-east-1 -Z us-east-1a --node-name aws2013 --distro
ubuntu10.04-ruby187

AWS · GitHub
http://d.pr/i/n6Pg

I expect to be able to create new servers and assign them to a
particular environment - is this correct?

Am I misunderstanding something or is something odd going on?

On Thu, Jan 10, 2013 at 2:25 PM, Darron Froese darron@froese.org wrote:

Using chef 10.16.4.

I have an environment called 'lucid' for my current infrastructure:

[master] darron@~/Dropbox/src/chef-repo: knife environment list
_default
lucid

We're using hosted Chef and this next bit shows all of my cookbook
versions for that environment:

gist:4505868 · GitHub

I'm adding a new server using that environment - tried passing
environment along 2 different ways:

bundle exec knife rackspace server create -E lucid -S server2013 -f 4
-N server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193

OR

bundle exec knife rackspace server create -S server2013 -f 4 -N
server2013 --image 112 -r
'role[setup],role[mysql_server],role[web_server],recipe[backup]'
--distro ubuntu10.04-ruby193 --environment lucid

Neither seems to work as I expect.

The server gets created, but at the end of the run, it says:

Name: server2013
Flavor: 2GB server
Image: Ubuntu 10.04 LTS
Metadata: {}
Environment: lucid
Run List: role[setup], role[mysql_server], role[web_server],
recipe[backup]

But:

It uses the 2.0.4 sudo cookbook that I uploaded yesterday - which
is not part of the lucid environment.

In the Opscode management interface it shows up as _default:
http://d.pr/i/UoZz

Any ideas what I'm missing?

Topic		Replies	Views
Running chef in multiple environments Chef Infra (archive)	17	420	August 1, 2014
Setting an environment for a chef-solo run Chef Infra (archive)	2	383	September 10, 2013
Chef Infra (archive)	0	239	April 27, 2015
Information related chef Chef Infra (archive)	2	665	September 9, 2016
Reconcile chef environment settings done on Chef web management interface with chef workstation Chef Infra (archive)	3	288	October 22, 2013

Hosted chef not honoring passed environment?

Using default node name"

Related Topics