knife - Why Aren't My Chef Normal Attributes Persisted? -


i need persist values between runs of chef-client on node. chef docs thought normal attributes intended

"at beginning of chef-client run, default, override, , automatic attributes reset...normal attributes never reset...at conclusion of chef-client run, default, override, , automatic attributes disappear, leaving collection of normal attributes persist until next chef-client run.")

however, if bootstrap node following recipe twice

log 'message'   message "before setting #{node['my_key']}"   level :warn end  node.normal['my_key'] = 'my value'  log 'message'   message "after setting #{node['my_key']}"   level :warn end

i expect see

before setting value

on 2nd run (as value persisted 1st run). reverts unset again.

is possible value persist? need run recipe in different way? or not possible?

edit: far can see chef run completes successfully. here command , output:

mfreake@my-linux:/export/apps/chef/chef-repo/cookbooks$ knife bootstrap node1.blah.com --ssh-user mfreake --ssh-password 'yaddayadda' --sudo --use-sudo-password  --bootstrap-proxy 'http://proxy.blah.com/' -n node1 --run-list persist_test::read_set_read node node1 exists, overwrite it? (y/n) y client node1 exists, overwrite it? (y/n) y creating new client node1 creating new node node1 connecting node1.marketpipe.com node1.blah.com [sudo] password mfreake: -----> existing chef installation detected node1.blah.com starting first chef client run... node1.blah.com starting chef client, version 12.4.2 node1.blah.com resolving cookbooks run list: ["persist_test::read_set_read"] node1.blah.com synchronizing cookbooks: node1.blah.com   - persist_test node1.blah.com compiling cookbooks... node1.blah.com [2015-09-30t17:45:40+01:00] warn: cloning resource attributes log[message] prior resource (chef-3694) node1.blah.com [2015-09-30t17:45:40+01:00] warn: previous log[message]: /var/chef/cache/cookbooks/persist_test/recipes/read_set_read.rb:2:in `from_file' node1.blah.com [2015-09-30t17:45:40+01:00] warn: current  log[message]: /var/chef/cache/cookbooks/persist_test/recipes/read_set_read.rb:9:in `from_file' node1.blah.com converging 2 resources node1.blah.com recipe: persist_test::read_set_read node1.blah.com   * log[message] action write[2015-09-30t17:45:40+01:00] warn: message add log.  node1.blah.com  node1.blah.com    node1.blah.com   * log[message] action write[2015-09-30t17:45:40+01:00] warn: message add log. value node1.blah.com  node1.blah.com    node1.blah.com  node1.blah.com running handlers: node1.blah.com running handlers complete node1.blah.com chef client finished, 2/2 resources updated in 1.621458795 seconds

ok, there's 2 cases node state, including attributes not saved on chef-server:

  1. when run end in error (here depending on error, state saved anyway, it's out of scope question)
  2. running chef-client -o any_recipe_list -ooption here temporarily override runlist, won't save chef-server not overwrite actual run list.

node.normal , node.set same thing, writing values in node object stored on server. examples in documentation on attributes

here problem due use of knife bootstrap (with version > 12.1 per documentation on validator less bootstrap) start creating node on chef-server , client key. calling twice , allowing overwrite previous object reset whole node object.

the bootstrap shoudl used once, chef-client run later should triggered way (crontab, knife ssh, etc.)


Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more