BREAKING: Enable packagecloud repos by default #324
Triggered via pull request
December 19, 2023 09:30
Status
Failure
Total duration
18m 40s
Artifacts
–
ci.yml
on: pull_request
Puppet
/
Static validations
23s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
0s
Annotations
6 errors and 9 warnings
Puppet / 7 - Debian 10:
spec/acceptance/delete_guest_user_spec.rb#L7
rabbitmq with delete_guest_user delete_guest_user runs successfully
Failure/Error: apply_manifest(pp, catch_failures: true)
Beaker::Host::CommandFailure:
Host 'debian10-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_093913020.pp.QWy8qM
Last 10 lines of output were:
Info: Class[Rabbitmq::Service]: Unscheduling all events on Class[Rabbitmq::Service]
�[mNotice: /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest]: Dependency Service[rabbitmq-server] has failures: true
Warning: /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest]: Skipping because of failed dependencies
Info: Class[Rabbitmq]: Unscheduling all events on Class[Rabbitmq]
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Package[python]: Skipping because of failed dependencies
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Exec[remove_old_rabbitmqadmin_on_upgrade]: Skipping because of failed dependencies
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Archive[rabbitmqadmin]: Skipping because of failed dependencies
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/File[/usr/local/bin/rabbitmqadmin]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 55.17 seconds
|
Puppet / 7 - Debian 10:
spec/acceptance/delete_guest_user_spec.rb#L21
rabbitmq with delete_guest_user delete_guest_user File "/tmp/rabbitmqctl_users" is expected to be file
Failure/Error: it { is_expected.to be_file }
expected `File "/tmp/rabbitmqctl_users".file?` to be truthy, got false
|
Puppet / 7 - Debian 10
Process completed with exit code 1.
|
Puppet / 7 - Ubuntu 18.04:
spec/acceptance/delete_guest_user_spec.rb#L7
rabbitmq with delete_guest_user delete_guest_user runs successfully
Failure/Error: apply_manifest(pp, catch_failures: true)
Beaker::Host::CommandFailure:
Host 'ubuntu1804-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_093936790.pp.D1joNs
Last 10 lines of output were:
Info: Class[Rabbitmq::Service]: Unscheduling all events on Class[Rabbitmq::Service]
�[mNotice: /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest]: Dependency Service[rabbitmq-server] has failures: true
Warning: /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest]: Skipping because of failed dependencies
Info: Class[Rabbitmq]: Unscheduling all events on Class[Rabbitmq]
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Package[python]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Exec[remove_old_rabbitmqadmin_on_upgrade]: Skipping because of failed dependencies
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Archive[rabbitmqadmin]: Skipping because of failed dependencies
Warning: /Stage[main]/Rabbitmq::Install::Rabbitmqadmin/File[/usr/local/bin/rabbitmqadmin]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 54.66 seconds
|
Puppet / 7 - Ubuntu 18.04:
spec/acceptance/delete_guest_user_spec.rb#L21
rabbitmq with delete_guest_user delete_guest_user File "/tmp/rabbitmqctl_users" is expected to be file
Failure/Error: it { is_expected.to be_file }
expected `File "/tmp/rabbitmqctl_users".file?` to be truthy, got false
|
Puppet / 7 - Ubuntu 18.04
Process completed with exit code 1.
|
Puppet / 7 - CentOS 7:
spec/acceptance/class_spec.rb#L118
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - CentOS 7:
spec/acceptance/class_spec.rb#L153
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - CentOS 7:
spec/acceptance/class_spec.rb#L218
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Debian 10:
spec/acceptance/class_spec.rb#L118
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Debian 10:
spec/acceptance/class_spec.rb#L153
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Debian 10:
spec/acceptance/class_spec.rb#L218
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Ubuntu 18.04:
spec/acceptance/class_spec.rb#L118
rabbitmq class: binding on all interfaces Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Ubuntu 18.04:
spec/acceptance/class_spec.rb#L153
rabbitmq class: binding to localhost only Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|
Puppet / 7 - Ubuntu 18.04:
spec/acceptance/class_spec.rb#L218
rabbitmq class: different management_ip_address and node_ip_address Port "25672" Is on 55672 instead on older rmq versions
Skipped: Temporarily skipped with xit
|