I’ve noticed that halting and restarting an EC2 instance causes it to
get new ip addresses and names.
The Chef server doesn’t know about this, and so it retains the old ec2
This really screws things up if you are using search to get dns names to
connect things together.
Re-running chef-client doesn’t seem to help, and also I can’t do it like
knife ssh ‘chef_environment:staging AND role:mongo_rs_member’ ‘sudo
… because of the very problem I’m trying to correct.
So … aside from just adjusting my expectations, is there any way to
update the nodes with the new correct ec2 information?