Connection refused on cloned host

[Harold Thurnstein]

Hi,

I have just cloned a VM and on the cloned VM I have changed the hostname and ip address. I have cleaned out /etc/puppet/ssl on the host, run a puppetca --clean 'new hostname' and have restarted the puppet master on the server. However when I run puppet  on the cloned host I get a connection refused. Is there some other file I should be removing as well? The version of puppet that we are running is 2.7.x and  the os is Red Hat 6. Thanks for any advice.

Harold.

[Felix Frank]

Hi,

that error message is a bit confusing.

Can you share the complete puppet agent --test output?

Note that SSL data usually resides in /var/lib/puppet/ssl, not /etc.

Thanks,
Felix

[jcbollinger]

On Thursday, June 5, 2014 7:10:50 AM UTC-5, Harold Thurnstein wrote:

Hi,

I have just cloned a VM and on the cloned VM I have changed the hostname and ip address. I have cleaned out /etc/puppet/ssl on the host, run a puppetca --clean 'new hostname' and have restarted the puppet master on the server. However when I run puppet  on the cloned host I get a connection refused. Is there some other file I should be removing as well? The version of puppet that we are running is 2.7.x and  the os is Red Hat 6. Thanks for any advice.

I don't think this is an SSL issue.  For one thing, if you exactly clone a VM, including its Puppet certificate, then it has a certificate that the master will accept.  Change the hostname / IP / whatever is not relevant to that.  The clone will impersonate the original to the master, so you generally don't want to leave it like that, but its hostname does not need to match the certificate name (that's a feature).

Connection refusal is more likely happening at the firewall or at the rack host.  The exact error message might shed some light on the specifics.


John