Steps to reproduce:
1. Run fuel-qa test 'deploy_ceilometer_ha_one_controller_with_mongo'.
2. Check astute.log during or after deployment
Expected results:
There is no errors in astute.log.
Actual result:
Deployment is successful, but there are a lot of such errors in astute.log:
2017-01-18 08:11:15 ERROR [6294] Exception during worker initialization: Connection-level error: CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', trace:
["/usr/share/gems/gems/astute-9.0.0/lib/astute/server/server.rb:57:in `join'",
"/usr/share/gems/gems/astute-9.0.0/lib/astute/server/server.rb:57:in `run'",
"/usr/share/gems/gems/astute-9.0.0/lib/astute/server/worker.rb:89:in `run_server'",
"/usr/share/gems/gems/astute-9.0.0/lib/astute/server/worker.rb:44:in `run'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:343:in `worker_loop!'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `block (2 levels) in spawn_workers'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `fork'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:266:in `block in spawn_workers'",
"/usr/share/gems/gems/activesupport-4.2.4/lib/active_support/core_ext/range/each.rb:7:in `each'",
"/usr/share/gems/gems/activesupport-4.2.4/lib/active_support/core_ext/range/each.rb:7:in `each_with_time_with_zone'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:261:in `spawn_workers'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:300:in `maintain_worker_count'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:120:in `master_loop!'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:53:in `start'",
"/usr/share/gems/gems/raemon-0.3.0/lib/raemon/master.rb:22:in `start'",
"/usr/share/gems/gems/astute-9.0.0/bin/astuted:83:in `<top (required)>'",
"-e:1:in `load'",
"-e:1:in `<main>'"]
All errors from astute.log: http://paste.openstack.org/show/595326/
Description of the environment:
9.2 snapshot #776
Additional information:
Also I've checked astute logs from master node for CI job (test 'deploy_ceilometer_ha_one_controller_with_mongo' included to this run):
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.services_ha_one_controller/174/
Tests are passed in this job, but result is the same - there are a lot of described errors in astute.log.
It it expected behavior. Astute service was run, but could not connect to RabbitMQ because it is missing or not configured. Astute report about such behavior into log and try to reconnect.
After successful connection Astute done his work without any errors.
It it really situation so recorded error should be into the log. I can remove backtrace for such error, so log will be more clean.