Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7162

CI acceptance: failure Huawei tests/pluingsync/7316_apps_should_be_available_via_pluginsync.rb

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 4.8.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Huawei

    • Template:
    • Team:
      Agent
    • QA Risk Assessment:
      Needs Assessment

      Description

      I was testing stable branch with SHA e32d6bf85e912c78a8b4f4d3266710666b972aba which hit the following failure in the manual CI pipeline on the Huawei box:

      tests/pluginsync.7316_apps_should_be_available_via_pluginsync.rb

      https://jenkins.puppetlabs.com/view/puppet-agent/view/manual/view/stable/job/platform_puppet-agent_intn-van-sys_suite-manual-puppet-stable/lastCompletedBuild/SLAVE_LABEL=beaker,TEST_TARGET=huaweios6-POWERaf%257Bhypervisor=none%252Chostname=huawei-ce6850-2-debian-vm-eth0.ops.puppetlabs.net%257D/testReport/junit/(root)/tests_pluginsync/7316_apps_should_be_available_via_pluginsync_rb/

      * run the agent
            
            huawei-ce6850-2-debian-vm-eth0.ops.puppetlabs.net 19:14:55$ puppet agent --libdir="/tmp/7316_apps_should_be_available_via_pluginsync.jSE3d0/agent_lib"  --test --trace --server lf43d40zvz8bcxj.delivery.puppetlabs.net
              Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: PRNG not seeded
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:62:in `random_bytes'
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:62:in `random_bytes'
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:242:in `uuid'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:295:in `initialize'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `new'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `to_catalog'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:995:in `use'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:401:in `setup'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `block in run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
              /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
              Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: PRNG not seeded
              PRNG not seeded
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:62:in `random_bytes'
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:62:in `random_bytes'
              /opt/puppetlabs/puppet/lib/ruby/2.1.0/securerandom.rb:242:in `uuid'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:295:in `initialize'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `new'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `to_catalog'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:995:in `use'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:401:in `setup'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `block in run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
              /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
              /opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
            
            huawei-ce6850-2-debian-vm-eth0.ops.puppetlabs.net executed in 5.08 seconds
            Exited: 1
       
      .....
       
      lf43d40zvz8bcxj.delivery.puppetlabs.net (redhat7-64-1) executed in 3.16 seconds
            RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'huawei-ce6850-2-debian-vm-eth0.ops.puppetlabs.net' exited with 1 running:
             puppet agent --libdir="/tmp/7316_apps_should_be_available_via_pluginsync.jSE3d0/agent_lib"  --test --trace --server lf43d40zvz8bcxj.delivery.puppetlabs.net
            Last 10 lines of output were:
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `new'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:929:in `to_catalog'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:995:in `use'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:401:in `setup'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `block in run'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:341:in `run'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run'
            	/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute'
            	/opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
      

        Attachments

          Activity

            People

            • Assignee:
              stan Stan Duffy
              Reporter:
              eric.delaney Eric Delaney
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support