We have a chef recipe that changes a node’s IP address. We’re using knife to execute the chef run, and not surprisingly, this has odd results after the IP address changes. Knife basically hangs because the machine was communicating with can’t be found.
I can’t imagine we’re the only people that have faced this. Any advice?
I use an seperate "add ip via recipe A", "remove ip via recipe B" cycle.
On Tue, May 01, 2012 at 10:21:48AM -0700, Paul McCallick wrote:
We have a chef recipe that changes a node's IP address. We're using knife to execute the chef run, and not surprisingly, this has odd results after the IP address changes. Knife basically hangs because the machine was communicating with can't be found.
I can't imagine we're the only people that have faced this. Any advice?
--
Markus Schirp
Phone: +49 201 / 360 379 14
Fax: +49 201 / 360 379 16
Web: www.seonic.net
Email: mbj@seonic.net
Twitter: twitter.com/m_b_j
OS-Code: mbj (Markus Schirp) · GitHub
Seonic IT-Systems GbR
Anton Shatalov & Markus Schirp
Altendorferstrasse 44
D-45127 Essen