I promise, I’ll get back to that soon, but in the meantime I encountered an issue that needed fixed and required a little more than the docs provided.I ran into an issue recently with Puppet Enterprise agents that weren’t able to purge some resource types properly due to the use of Anchors.If you have the public key of the server you're about to connect to, you can add it to on the client manually.Authenticating the server has to be done before you send any confidential data to it.You will need to delete the key from your directory by doing the following: From your Terminal window: You should have a prompt that ends with a $ sign. It will be formatted as first an IP address followed by the keys associated with that address. Is there a way that I can bypass this and get the new host to be already known to the client machine, maybe by using a public key that's already baked into the virtual machine image ? On my primary partition (there is no special /home) I have only 3% usage. If I run ssh with -vvv I don't get any extra information between it asking if I want to connect and warning me that it is permanently added to known hosts (which we've determined is a lie).
ECDSA key fingerprint is d4:a2:cf:42:0b:01:xx:e5:xx:7a:xx:93:xx:53:xx:b4. Are you sure you want to continue connecting (yes/no)? This is an issue with Puppet, not the module in question, and it was fixed in Puppet 4.4.0 but affected nodes were running older versions.Of course, rather than upgrade the agents by hand, I decided to automate it.If there is no entry already in place on your machine, you will simply be prompted to approve the connection by entering ‘yes’ at the prompt.However, if you already have a key in your This requires a more aggressive approach. This will open a text editor that displays all of your keys.