Puppet Community

I have agent nodes on my old puppet master which have not migrated to my new puppet master after running a migration

What is the best way to resolve this issue making sure any nodes missed are being carried over

I printed out the hostname on the missing agent node and it says puppet so i assumed after the dns cutover, everything would just be looking at the new puppet server

Every `puppet` agent run opens a new network connection to the server, so `puppet` should eventually resolve to the new IP address after DNS caches expire.

If that isn't happening, that would indicate the hostname data those agents are receiving has not been updated with the new IP address for the `puppet` hostname.

<https://www.cyberciti.biz/media/new/cms/2017/04/dns.jpg>

If that isn't happening, that would indicate the hostname data those agents are receiving has not been updated with the new IP address for the `puppet` hostname. How to resolve this issue

Those agents do not exist on the new host at all so confused on the best process to fix this

point them to the FQDN of the new server. don't use `puppet` (which you probably injected in /etc/hosts?)

You can check by running `getent hosts puppet` or `nslookup puppet` on the nodes that aren't connecting in. If that returns the old IP address, then you need to update the hostname data.

How to make that update is 100% a site-specific operation. Punching it into an UI, updating a BIND zone database, etc.

and you can use a bolt plan to update the puppet.conf on the agents for the new server FQDN and then start an agent run

I used `nslookup puppet on one of the nodes`

It is indicating the new host but yet puppet does not have that node in it's list (The NEW PUPPET)

use a bolt plan to update the puppet.conf on the agents for the new server FQDN and then start an agent run - please explain

that should containt `server = <http://foo.local.something.com|foo.local.something.com>`

Ok, if `nslookup puppet` returns the new IP address, does `puppet agent -t` run without error?

ensure that every puppet.conf contains the new FQDN

Then the agent checked into the new server successfully.