Uploaded image for project: 'Puppet Communications Protocol'
  1. Puppet Communications Protocol
  2. PCP-593

Seen once: pcp-broker not started within 1 minute in pxp-agent acceptance

    XMLWordPrintable

    Details

    • Template:
    • Team:
      Dumpling

      Description

      https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-pxp-agent-1.7.0-release/SLAVE_LABEL=beaker,TEST_TARGET=osx1011-64a/8/testReport/junit/(root)/setup_common/050_Setup_Broker_rb/

          Retrieving com/taoensso/encore/1.32.0/encore-1.32.0.jar from internal-clojars-mirror
          Retrieving slingshot/slingshot/0.12.2/slingshot-0.12.2.jar from internal-clojars-mirror
          Retrieving org/clojars/smee/binary/0.3.0/binary-0.3.0.jar from internal-clojars-mirror
          Retrieving clamq/clamq-jms/0.4/clamq-jms-0.4.jar from internal-clojars-mirror
          Retrieving clamq/clamq-activemq/0.4/clamq-activemq-0.4.jar from internal-clojars-mirror
          Retrieving puppetlabs/pcp-common/0.5.4/pcp-common-0.5.4.jar from internal-clojars-mirror
          Retrieving clamq/clamq-core/0.4/clamq-core-0.4.jar from internal-clojars-mirror
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 22.09 seconds
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:42:59$ cd /opt/puppet-git-repos/pcp-broker1; export LEIN_ROOT=ok; lein with-profile internal-mirrors deps
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 2.28 seconds
       
      * Run pcp-broker on master in trapperkeeper in background and wait for it to report status 'running'
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:43:01$ sed --in-place'' --regexp-extended 's/ssl-port:\s?[0-9]+/ssl-port: 8142/' /opt/puppet-git-repos/pcp-broker0/test-resources/conf.d/webserver.conf
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 0.01 seconds
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:43:01$ sed --in-place'' --regexp-extended 's/port\s?=\s?[0-9]+/port = 7888/' /opt/puppet-git-repos/pcp-broker0/test-resources/conf.d/nrepl.conf
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 0.01 seconds
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:43:01$ sed --in-place'' --regexp-extended 's/ssl-port:\s?[0-9]+/ssl-port: 8143/' /opt/puppet-git-repos/pcp-broker1/test-resources/conf.d/webserver.conf
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 0.01 seconds
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:43:01$ sed --in-place'' --regexp-extended 's/port\s?=\s?[0-9]+/port = 7889/' /opt/puppet-git-repos/pcp-broker1/test-resources/conf.d/nrepl.conf
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 0.01 seconds
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) 15:43:01$ cd /opt/puppet-git-repos/pcp-broker0; export LEIN_ROOT=ok; lein tk </dev/null >/var/log/pcp-broker.log 2>&1 &
        
        nctafkjilg7mal1.delivery.puppetlabs.net (redhat7-64-1) executed in 0.01 seconds
        Minitest::Assertion: pcp-broker port 8142 not open within 1 minutes of starting the broker
        /var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-daily-pxp-agent-1.7.0-release/SLAVE_LABEL/beaker/TEST_TARGET/osx1011-64a/pxp-agent/acceptance/setup/common/050_Setup_Broker.rb:66
        /var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-daily-pxp-agent-1.7.0-release/SLAVE_LABEL/beaker/TEST_TARGET/osx1011-64a/pxp-agent/acceptance/setup/common/050_Setup_Broker.rb:60
        /var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-daily-pxp-agent-1.7.0-release/SLAVE_LABEL/beaker/TEST_TARGET/osx1011-64a/pxp-agent/acceptance/.bundle/gems/gems/beaker-2.51.0/bin/beaker:6
        Begin teardown
        End teardown

      This is the same problem that was reported in PCP-557. I don't want to re-open that ticket as Michael Smith identified and fixed a definite problem there

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              james.stocks James Stocks
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support