Skip to content

Instantly share code, notes, and snippets.

@jcoconnor
Created October 19, 2016 16:25
Show Gist options
  • Save jcoconnor/445a1488502168f0a4a4150e0c4f5350 to your computer and use it in GitHub Desktop.
Save jcoconnor/445a1488502168f0a4a4150e0c4f5350 to your computer and use it in GitHub Desktop.
Beaker Aint Nice
No cumulus hosts present
Warning: setup/aio/pre-suite/020_InstallCumulusModules.rb skipped in 0.00 seconds
Begin setup/aio/pre-suite/021_InstallAristaModule.rb
No arista hosts present
Warning: setup/aio/pre-suite/021_InstallAristaModule.rb skipped in 0.00 seconds
Begin setup/common/pre-suite/025_StopFirewall.rb
Stop firewall
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:53$ puppet resource service iptables ensure=stopped
service { 'iptables':
ensure => 'stopped',
}
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 1.85 seconds
Not sure how to clear firewall on windows-2012-x86_64.pending
setup/common/pre-suite/025_StopFirewall.rb passed in 1.85 seconds
Begin setup/common/pre-suite/040_ValidateSignCert.rb
Validate Sign Cert
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:55$ facter hostname
kli3xwfnqyuy24e
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.36 seconds
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:56$ facter fqdn
kli3xwfnqyuy24e.delivery.puppetlabs.net
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.36 seconds
* Ensure puppet is stopped
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:56$ puppet resource service puppetserver ensure=stopped
service { 'puppetserver':
ensure => 'stopped',
}
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 1.27 seconds
* Clear SSL on all hosts
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:57$ puppet agent --configprint ssldir
/etc/puppetlabs/puppet/ssl
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 1.05 seconds
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:23:58$ rm -rf '/etc/puppetlabs/puppet/ssl'
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.30 seconds
cm6e5dmybihiz1z.delivery.puppetlabs.net (windows-2012) 17:23:59$ cmd.exe /c puppet agent --configprint ssldir
C:/ProgramData/PuppetLabs/puppet/etc/ssl
cm6e5dmybihiz1z.delivery.puppetlabs.net (windows-2012) executed in 1.42 seconds
cm6e5dmybihiz1z.delivery.puppetlabs.net (windows-2012) 17:24:00$ rm -rf 'C:/ProgramData/PuppetLabs/puppet/etc/ssl'
cm6e5dmybihiz1z.delivery.puppetlabs.net (windows-2012) executed in 0.37 seconds
* Master: Start Puppet Master
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:24:00$ mktemp -dt 040_ValidateSignCert.rb.XXXXXX
/tmp/040_ValidateSignCert.rb.uADDm9
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.44 seconds
Setting curl retries to 30
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:24:01$ puppet master --configprint confdir
/etc/puppetlabs/puppet
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 1.02 seconds
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:24:02$ puppet master --configprint vardir
/opt/puppetlabs/server/data/puppetserver
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 1.01 seconds
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:24:03$ test -e /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.30 seconds
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) 17:24:03$ cat /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf
# configuration for the JRuby interpreters
jruby-puppet: {
# Where the puppet-agent dependency places puppet, facter, etc...
# Puppet server expects to load Puppet from this location
ruby-load-path: [/opt/puppetlabs/puppet/lib/ruby/vendor_ruby]
# This setting determines where JRuby will install gems. It is used for loading gems,
# and also by the `puppetserver gem` command line tool.
gem-home: /opt/puppetlabs/server/data/puppetserver/jruby-gems
# This setting defines the complete "GEM_PATH" for jruby. If set, it should include
# the gem-home directory as well as any other directories that gems can be loaded
# from (including the vendored gems directory for gems that ship with puppetserver)
gem-path: [${jruby-puppet.gem-home}, "/opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems"]
# PLEASE NOTE: Use caution when modifying the below settings. Modifying
# these settings will change the value of the corresponding Puppet settings
# for Puppet Server, but not for the Puppet CLI tools. This likely will not
# be a problem with master-var-dir, master-run-dir, or master-log-dir unless
# some critical setting in puppet.conf is interpolating the value of one
# of the corresponding settings, but it is important that any changes made to
# master-conf-dir and master-code-dir are also made to the corresponding Puppet
# settings when running the Puppet CLI tools. See
# https://docs.puppetlabs.com/puppetserver/latest/puppet_conf_setting_diffs.html#overriding-puppet-settings-in-puppet-server
# for more information.
# (optional) path to puppet conf dir; if not specified, will use
# /etc/puppetlabs/puppet
master-conf-dir: /etc/puppetlabs/puppet
# (optional) path to puppet code dir; if not specified, will use
# /etc/puppetlabs/code
master-code-dir: /etc/puppetlabs/code
# (optional) path to puppet var dir; if not specified, will use
# /opt/puppetlabs/server/data/puppetserver
master-var-dir: /opt/puppetlabs/server/data/puppetserver
# (optional) path to puppet run dir; if not specified, will use
# /var/run/puppetlabs/puppetserver
master-run-dir: /var/run/puppetlabs/puppetserver
# (optional) path to puppet log dir; if not specified, will use
# /var/log/puppetlabs/puppetserver
master-log-dir: /var/log/puppetlabs/puppetserver
# (optional) maximum number of JRuby instances to allow
#max-active-instances: 1
# (optional) Authorize access to Puppet master endpoints via rules specified
# in the legacy Puppet auth.conf file (if true or not specified) or via rules
# specified in the Puppet Server HOCON-formatted auth.conf (if false).
#use-legacy-auth-conf: false
}
# settings related to HTTP client requests made by Puppet Server
http-client: {
# A list of acceptable protocols for making HTTP requests
#ssl-protocols: [TLSv1, TLSv1.1, TLSv1.2]
# A list of acceptable cipher suites for making HTTP requests
#cipher-suites: [TLS_RSA_WITH_AES_256_CBC_SHA256,
# TLS_RSA_WITH_AES_256_CBC_SHA,
# TLS_RSA_WITH_AES_128_CBC_SHA256,
# TLS_RSA_WITH_AES_128_CBC_SHA]
}
# settings related to profiling the puppet Ruby code
profiler: {
# enable or disable profiling for the Ruby code; defaults to 'false'.
#enabled: true
}
kli3xwfnqyuy24e.delivery.puppetlabs.net (master) executed in 0.44 seconds
Try Hocon on # configuration for the JRuby interpreters
jruby-puppet: {
# Where the puppet-agent dependency places puppet, facter, etc...
# Puppet server expects to load Puppet from this location
ruby-load-path: [/opt/puppetlabs/puppet/lib/ruby/vendor_ruby]
# This setting determines where JRuby will install gems. It is used for loading gems,
# and also by the `puppetserver gem` command line tool.
gem-home: /opt/puppetlabs/server/data/puppetserver/jruby-gems
# This setting defines the complete "GEM_PATH" for jruby. If set, it should include
# the gem-home directory as well as any other directories that gems can be loaded
# from (including the vendored gems directory for gems that ship with puppetserver)
gem-path: [${jruby-puppet.gem-home}, "/opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems"]
# PLEASE NOTE: Use caution when modifying the below settings. Modifying
# these settings will change the value of the corresponding Puppet settings
# for Puppet Server, but not for the Puppet CLI tools. This likely will not
# be a problem with master-var-dir, master-run-dir, or master-log-dir unless
# some critical setting in puppet.conf is interpolating the value of one
# of the corresponding settings, but it is important that any changes made to
# master-conf-dir and master-code-dir are also made to the corresponding Puppet
# settings when running the Puppet CLI tools. See
# https://docs.puppetlabs.com/puppetserver/latest/puppet_conf_setting_diffs.html#overriding-puppet-settings-in-puppet-server
# for more information.
# (optional) path to puppet conf dir; if not specified, will use
# /etc/puppetlabs/puppet
master-conf-dir: /etc/puppetlabs/puppet
# (optional) path to puppet code dir; if not specified, will use
# /etc/puppetlabs/code
master-code-dir: /etc/puppetlabs/code
# (optional) path to puppet var dir; if not specified, will use
# /opt/puppetlabs/server/data/puppetserver
master-var-dir: /opt/puppetlabs/server/data/puppetserver
# (optional) path to puppet run dir; if not specified, will use
# /var/run/puppetlabs/puppetserver
master-run-dir: /var/run/puppetlabs/puppetserver
# (optional) path to puppet log dir; if not specified, will use
# /var/log/puppetlabs/puppetserver
master-log-dir: /var/log/puppetlabs/puppetserver
# (optional) maximum number of JRuby instances to allow
#max-active-instances: 1
# (optional) Authorize access to Puppet master endpoints via rules specified
# in the legacy Puppet auth.conf file (if true or not specified) or via rules
# specified in the Puppet Server HOCON-formatted auth.conf (if false).
#use-legacy-auth-conf: false
}
# settings related to HTTP client requests made by Puppet Server
http-client: {
# A list of acceptable protocols for making HTTP requests
#ssl-protocols: [TLSv1, TLSv1.1, TLSv1.2]
# A list of acceptable cipher suites for making HTTP requests
#cipher-suites: [TLS_RSA_WITH_AES_256_CBC_SHA256,
# TLS_RSA_WITH_AES_256_CBC_SHA,
# TLS_RSA_WITH_AES_128_CBC_SHA256,
# TLS_RSA_WITH_AES_128_CBC_SHA]
}
# settings related to profiling the puppet Ruby code
profiler: {
# enable or disable profiling for the Ruby code; defaults to 'false'.
#enabled: true
}
Try inifile on # configuration for the JRuby interpreters
jruby-puppet: {
# Where the puppet-agent dependency places puppet, facter, etc...
# Puppet server expects to load Puppet from this location
ruby-load-path: [/opt/puppetlabs/puppet/lib/ruby/vendor_ruby]
# This setting determines where JRuby will install gems. It is used for loading gems,
# and also by the `puppetserver gem` command line tool.
gem-home: /opt/puppetlabs/server/data/puppetserver/jruby-gems
# This setting defines the complete "GEM_PATH" for jruby. If set, it should include
# the gem-home directory as well as any other directories that gems can be loaded
# from (including the vendored gems directory for gems that ship with puppetserver)
gem-path: [${jruby-puppet.gem-home}, "/opt/puppetlabs/server/data/puppetserver/vendored-jruby-gems"]
# PLEASE NOTE: Use caution when modifying the below settings. Modifying
# these settings will change the value of the corresponding Puppet settings
# for Puppet Server, but not for the Puppet CLI tools. This likely will not
# be a problem with master-var-dir, master-run-dir, or master-log-dir unless
# some critical setting in puppet.conf is interpolating the value of one
# of the corresponding settings, but it is important that any changes made to
# master-conf-dir and master-code-dir are also made to the corresponding Puppet
# settings when running the Puppet CLI tools. See
# https://docs.puppetlabs.com/puppetserver/latest/puppet_conf_setting_diffs.html#overriding-puppet-settings-in-puppet-server
# for more information.
# (optional) path to puppet conf dir; if not specified, will use
# /etc/puppetlabs/puppet
master-conf-dir: /etc/puppetlabs/puppet
# (optional) path to puppet code dir; if not specified, will use
# /etc/puppetlabs/code
master-code-dir: /etc/puppetlabs/code
# (optional) path to puppet var dir; if not specified, will use
# /opt/puppetlabs/server/data/puppetserver
master-var-dir: /opt/puppetlabs/server/data/puppetserver
# (optional) path to puppet run dir; if not specified, will use
# /var/run/puppetlabs/puppetserver
master-run-dir: /var/run/puppetlabs/puppetserver
# (optional) path to puppet log dir; if not specified, will use
# /var/log/puppetlabs/puppetserver
master-log-dir: /var/log/puppetlabs/puppetserver
# (optional) maximum number of JRuby instances to allow
#max-active-instances: 1
# (optional) Authorize access to Puppet master endpoints via rules specified
# in the legacy Puppet auth.conf file (if true or not specified) or via rules
# specified in the Puppet Server HOCON-formatted auth.conf (if false).
#use-legacy-auth-conf: false
}
# settings related to HTTP client requests made by Puppet Server
http-client: {
# A list of acceptable protocols for making HTTP requests
#ssl-protocols: [TLSv1, TLSv1.1, TLSv1.2]
# A list of acceptable cipher suites for making HTTP requests
#cipher-suites: [TLS_RSA_WITH_AES_256_CBC_SHA256,
# TLS_RSA_WITH_AES_256_CBC_SHA,
# TLS_RSA_WITH_AES_128_CBC_SHA256,
# TLS_RSA_WITH_AES_128_CBC_SHA]
}
# settings related to profiling the puppet Ruby code
profiler: {
# enable or disable profiling for the Ruby code; defaults to 'false'.
#enabled: true
}
RuntimeError: Error reading trapperkeeper config: /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf at host: kli3xwfnqyuy24e.delivery.puppetlabs.net
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/dsl/helpers/tk_helpers.rb:46
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/dsl/helpers/tk_helpers.rb:43
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/dsl/helpers/puppet_helpers.rb:159
/Users/johnoconnor/gitrepos/puppet/acceptance/lib/puppet/acceptance/common_utils.rb:51
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/dsl/structure.rb:43
/Users/johnoconnor/gitrepos/puppet/acceptance/lib/puppet/acceptance/common_utils.rb:41
/Users/johnoconnor/gitrepos/puppet/acceptance/setup/common/pre-suite/040_ValidateSignCert.rb:6
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_case.rb:128
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_case.rb:128
/Users/johnoconnor/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/benchmark.rb:303
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_case.rb:125
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_suite.rb:311
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_suite.rb:308
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_suite.rb:308
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/test_suite.rb:357
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/cli.rb:159
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/lib/beaker/cli.rb:95
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/gems/beaker-2.32.1/bin/beaker:6
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/bin/beaker:23
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/bin/beaker:23
Warning: setup/common/pre-suite/040_ValidateSignCert.rb errored in 8.35 seconds
Test Suite: pre_suite @ 2016-10-19 17:22:42 +0100
- Host Configuration Summary -
- Test Case Summary for suite 'pre_suite' -
Total Suite Time: 81.77 seconds
Average Test Time: 11.68 seconds
Attempted: 7
Passed: 4
Failed: 0
Errored: 1
Skipped: 2
Pending: 0
Total: 8
- Specific Test Case Status -
Failed Tests Cases:
Errored Tests Cases:
Test Case setup/common/pre-suite/040_ValidateSignCert.rb reported: #<RuntimeError: Error reading trapperkeeper config: /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf at host: kli3xwfnqyuy24e.delivery.puppetlabs.net>
Skipped Tests Cases:
Test Case setup/aio/pre-suite/020_InstallCumulusModules.rb skip
Test Case setup/aio/pre-suite/021_InstallAristaModule.rb skip
Pending Tests Cases:
Failed: errored in TestSuite: report_and_raise_on_failure
#<RuntimeError: Failed while running the pre_suite suite>
You can reproduce this run with:
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/bin/beaker --options-file merged_options.rb --hosts=win-4.yaml
You can re-run commands against the already provisioned SUT(s) with:
/Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/bin/beaker --options-file merged_options.rb --hosts=win-4.yaml
Important ENV variables that may have affected your run:
GEM_HOME /Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0
GEM_PATH
RUBYLIB /Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib
PATH /Users/johnoconnor/gitrepos/puppet/acceptance/.bundle/ruby/2.2.0/bin:/Users/johnoconnor/.rvm/gems/ruby-2.2.5/bin:/Users/johnoconnor/.rvm/gems/ruby-2.2.5@global/bin:/Users/johnoconnor/.rvm/rubies/ruby-2.2.5/bin:/Users/johnoconnor/.rvm/bin:/Users/johnoconnor/.pyenv/shims:/usr/local/opt/gnu-tar/libexec/gnubin:/usr/local/opt/coreutils/libexec/gnubin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin
home /Users/johnoconnor
Failed running the test suite.
rake aborted!
Command failed with status (1): [beaker --options-file merged_options.rb --...]
/Users/johnoconnor/gitrepos/puppet/acceptance/Rakefile:146:in `beaker_test'
/Users/johnoconnor/gitrepos/puppet/acceptance/Rakefile:341:in `block (3 levels) in <top (required)>'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli/exec.rb:74:in `load'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli/exec.rb:74:in `kernel_load'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli/exec.rb:27:in `run'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli.rb:332:in `exec'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli.rb:20:in `dispatch'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/cli.rb:11:in `start'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/exe/bundle:34:in `block in <top (required)>'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/lib/bundler/friendly_errors.rb:100:in `with_friendly_errors'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/gems/bundler-1.13.5/exe/bundle:26:in `<top (required)>'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/bin/bundle:23:in `load'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/bin/bundle:23:in `<main>'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/bin/ruby_executable_hooks:15:in `eval'
/Users/johnoconnor/.rvm/gems/ruby-2.2.5/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => ci:test:aio
(See full trace by running task with --trace)
johnoconnor@Johns-MacBook-Pro-4:~/gitrepos/puppet/acceptance [(5fd37e3...) %] 17:24:04 $ gst
HEAD detached at 5fd37e3
Untracked files:
(use "git add <file>..." to include in what will be committed)
win-1.yaml
win-4.yaml
win-5.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment