Skip to content

Apply jvm_nofiles_limit to systemd service #310

Apply jvm_nofiles_limit to systemd service

Apply jvm_nofiles_limit to systemd service #310

Triggered via pull request June 12, 2024 13:03
Status Failure
Total duration 21m 46s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
30s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
0s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

9 errors
Puppet / Puppet 7 - CentOS 8
Process completed with exit code 1.
Puppet / Puppet 8 - CentOS 8
Process completed with exit code 1.
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L6
jira mysql installs with defaults Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_131658003.8B6ToY.pp Last 10 lines of output were: Warning: /Stage[main]/Jira::Config/File[/opt/atlassian-jira/atlassian-jira-software-8.13.5-standalone/bin/check-java.sh]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Config/File[/opt/atlassian-jira/atlassian-jira-software-8.13.5-standalone/conf/server.xml]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Config/File[/opt/atlassian-jira/atlassian-jira-software-8.13.5-standalone/conf/context.xml]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Config/File[/opt/jira-home/jira-config.properties]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Service/Systemd::Unit_file[jira.service]/File[/etc/systemd/system/jira.service]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Service/Systemd::Unit_file[jira.service]/Systemd::Daemon_reload[jira.service]/Exec[systemd-jira.service-systemctl-daemon-reload]: Skipping because of failed dependencies Warning: /Stage[main]/Jira::Service/Service[jira]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] Error: Could not find a suitable provider for mysql_datadir �[mNotice: Applied catalog in 112.15 seconds
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L116
jira mysql is expected to have attributes {:stdout => /8.13.5/} Failure/Error: expect(command('wget -q --tries=24 --retry-connrefused --no-check-certificate --read-timeout=10 -O- localhost:8081')). to have_attributes(stdout: %r{8.13.5}) expected Command "wget -q --tries=24 --retry-connrefused --no-check-certificate --read-timeout=10 -O- localhost:8081" to have attributes {:stdout => /8.13.5/} but had attributes {:stdout => ""} Diff: @@ -1 +1 @@ -:stdout => /8.13.5/, +:stdout => "",
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L121
jira mysql is expected to have attributes {:stdout => /8.13.5/} Failure/Error: expect(command('wget -q --tries=24 --retry-connrefused --no-check-certificate --read-timeout=10 -O- https://localhost:8443')). to have_attributes(stdout: %r{8.13.5}) expected Command "wget -q --tries=24 --retry-connrefused --no-check-certificate --read-timeout=10 -O- https://localhost:8443" to have attributes {:stdout => /8.13.5/} but had attributes {:stdout => ""} Diff: @@ -1 +1 @@ -:stdout => /8.13.5/, +:stdout => "",
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L99
jira mysql Process "java" is expected to be running Failure/Error: it { is_expected.to be_running } expected Process "java" to be running
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L103
jira mysql Port "8081" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "8081" to be listening
Puppet / Puppet 8 - Ubuntu 20.04: spec/acceptance/mysql_spec.rb#L108
jira mysql Service "jira" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "jira" to be running
Puppet / Puppet 8 - Ubuntu 20.04
Process completed with exit code 1.