Jira (PDB-3232) Open ports for PuppetDB based on assigned listen address

Valery Zabawski (JIRA)

unread,

Dec 19, 2016, 10:36:05 AM12/19/16

to puppe...@googlegroups.com

Valery Zabawski updated an issue

PuppetDB /

PDB-3232

Open ports for PuppetDB based on assigned listen address

Change By:	Valery Zabawski
Priority:	Blocker Trivial
Summary:	Unable to connect to puppetdb while using Open ports for PuppetDB module based on assigned listen address
Issue Type:	Bug New Feature

site.pp file:
{code:title=site.pp|borderStyle=solid}
node default {}
node 'test-puppet-server puppetserver . 3o0xhk5vf2juflemmtk4pgc3le example . bx.internal.cloudapp.net com ' {
    class { 'puppetmodules': }
    class { 'puppetdb::master::config':
    puppetdb_server => '10.0.0.10',
  }
}

node ' test-puppet-db puppetdb . 3o0xhk5vf2juflemmtk4pgc3le example . bx.internal.cloudapp.net com ' {

    class { 'puppetdb': }

}
{code}
Installation on PuppetDB node performst without any problems, netstat shows port is listening
{code}tcp6       0      0 :::8081                 :::*                    LISTEN      5960/java{code}

When running Puppet Agent on Puppet Server the next error occurs:
{code:title=Output}
Notice: Unable to connect to puppetdb server (https://10.0.0.10:8081): No route to host - connect(2) for "10.0.0.10" port 8081
Notice: Failed to connect to puppetdb; sleeping 2 seconds before retry
Error: Unable to connect to puppetdb server! (10.0.0.10:8081)
Error: /Stage[main]/Puppetdb::Master::Config/Puppetdb_conn_validator[puppetdb_conn]/ensure: change from absent to present failed: Unable to connect to puppetdb server! (10.0.0.10:8081)
{code}
Server pings PuppetDB successfully. Jetty ssl-host is set to 0.0.0.0, ssl-port is set to 8081 by PuppetDB module on PuppetDB node.
{code}cat < /dev/tcp/10.0.0.10/22
SSH-2.0-OpenSSH_6.6.1
cat < /dev/tcp/10.0.0.10/8081
-bash: connect: No route to host
-bash: /dev/tcp/10.0.0.10/8081: No route to host
{code}

I've tried to use "Prefer IPv4" argument in JAVA_ARGS of PuppetDB but The problem is iptables were working though firewalld was stopped, so it didn't worked for me would be nice if module was automatically managing firewall rules based on ip address and port settings .