Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1258

Master failing acceptance in puppetdb_integration.rb

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: SERVER 2.y
    • Fix Version/s: SERVER 2.4.0
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      2
    • Sprint:
      Server Jade 2016-04-20

      Description

      Not sure what's happening here yet, but https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_smoke-master/ is failing because it attempts to redefine an entity and PuppetDB objects: (https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_smoke-master/221/LAYOUT=centos6-64ma-32a,LDAP_TYPE=default,PLATFORM=default,label=beaker/):

      Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet_x/apt_key/patch_openuri.rb]/ensure: defined content as '{md5}951bad007a3b5db035be069c1d1c9c09'
      Info: Loading facts
      Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Type-Name, Attempt to redefine entity 'type/postgresql::server::pg_hba_rule' originally set at  Originally set at file:/etc/puppetlabs/code/environments/production/modules/postgresql/manifests/server/pg_hba_rule.pp?line=3&pos=1. at /etc/puppetlabs/code/environments/production/modules/postgresql/manifests/server/config.pp:36:7 on node xux3459a999sr8l.delivery.puppetlabs.net
      Warning: Not using cache on failed catalog
      Error: Could not retrieve catalog; skipping run
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              kurt.wall Kurt Wall
              QA Contact:
              Kurt Wall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support