Commis sends all cookbooks to a client on client start

[drax68]

Results from uwsgi log:
POST /api/environments/_default/cookbook_versions => generated 0 bytes in 255692 msecs (HTTP/1.1 200) 1 headers in 18446744073709551615 bytes (0 switches on core 0)

Chef-client log:
[Tue, 29 May 2012 09:04:33 +0000] INFO: *** Chef 0.10.8 *** [Tue, 29 May 2012 09:04:40 +0000] INFO: Setting the run_list to ["recipe[motd-tail]"] from JSON [Tue, 29 May 2012 09:04:40 +0000] INFO: Run List is [recipe[motd-tail]] [Tue, 29 May 2012 09:04:40 +0000] INFO: Run List expands to [motd-tail] [Tue, 29 May 2012 09:04:40 +0000] INFO: Starting Chef Run for chef-client-node [Tue, 29 May 2012 09:04:40 +0000] INFO: Running start handlers [Tue, 29 May 2012 09:04:40 +0000] INFO: Start handlers complete. [Tue, 29 May 2012 09:08:55 +0000] INFO: Loading cookbooks [all_82_cookbooks_stored_in_commis] [Tue, 29 May 2012 09:09:06 +0000] INFO: Processing template[/etc/motd.tail] action create (motd-tail::default line 23) [Tue, 29 May 2012 09:09:15 +0000] INFO: Chef Run complete in 274.841949 seconds [Tue, 29 May 2012 09:09:15 +0000] INFO: Running report handlers [Tue, 29 May 2012 09:09:15 +0000] INFO: Report handlers complete

[bitprophet]

Paging @coderanger; I noticed this myself, during testing, but wasn't sure if that was the normal behavior for Chef Server or not. Guessing "not"...

(I feel I should probably set up a "real" Chef Server to sanity-check this stuff, or sign up for hosted Chef ;))