XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Declined
    • PE 3.3.1
    • None
    • Agent Installer
    • Chrome
    • Monolithic
    • Ubuntu 14.04 (amd64)

    Description

      I'm running puppet enterprise 3.3.1 on master/nodes running Ubuntu 14.04.1.

      This is the puppet.conf on the master:

      root@puppet:~# cat /etc/puppetlabs/puppet/puppet.conf
      [main]
      certname = puppet.openstacklocal
      dns_alt_names = puppet,puppet.lan
      vardir = /var/opt/lib/pe-puppet
      logdir = /var/log/pe-puppet
      rundir = /var/run/pe-puppet
      basemodulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
      server = puppet.openstacklocal
      user = pe-puppet
      group = pe-puppet
      archive_files = true
      archive_file_server = puppet.openstacklocal

      [master]
      certname = puppet.openstacklocal
      ca_name = 'Puppet CA generated on puppet at 2014-08-14 05:03:59 +0000'
      reports = console,puppetdb
      node_terminus = console
      ssl_client_header = SSL_CLIENT_S_DN
      ssl_client_verify_header = SSL_CLIENT_VERIFY
      storeconfigs = true
      storeconfigs_backend = puppetdb

      [agent]
      report = true
      classfile = $vardir/classes.txt
      localconfig = $vardir/localconfig
      graph = true
      pluginsync = true
      environment = production

      All nodes work fine except for 1:

      root@search:~# puppet agent -t
      Warning: Unable to fetch my node definition, but the agent run will continue:
      Warning: Error 400 on SERVER: Error 406 while communicating with puppet.openstacklocal on port 443:

      Info: Retrieving plugin
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/platform_tag.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/postgres_default_version.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_puppetdb_server_status.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_persistent_version.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/ip6tables_version.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/windows.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_postgres_default_version.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_build.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
      Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_version.rb
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node search.openstacklocal: Error 406 while communicating with puppet.openstacklocal on port 443:

      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run

      I can telnet fine to port 443 from the agent to the master:

      root@search:~# telnet puppet.openstacklocal 443
      Trying 10.10.21.5...
      Connected to puppet.lan.
      Escape character is '^]'.

      ^]
      telnet> quit

      It gets added to the dashboard but the reports are all empty. I tried several times to remove and reinstall the pe-puppet agent and packages as well as reinstalling the puppet master from scratch but I always get the same error.

      I searched all over for the combination of error 400, error 406 and port 443 but didn't find anything useful.

      Attachments

        Activity

          People

            patrick.maddox Patrick Maddox
            edvar Ed Lima
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support