The nagios charm fails automated testing

Bug #1403574 reported by Matt Bruzek on 2014-12-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nagios (Juju Charms Collection)
Matt Bruzek

Bug Description

In an effort to improve quality, we are testing all charms in an automated process.

According to the latest test results by charm this charm is failing automated testing.

The latest automated test results can be found here:

It looks like the 100-deploy test fails on all environments with the following output:

2014-11-04 04:42:41 The following units had errors:
   unit: nagios/0: machine: 3 agent-state: error details: hook failed: "install"

Please investigate and fix the charm or the test so the automated tests pass.

Matt Bruzek (mbruzek) on 2014-12-17
Changed in nagios (Juju Charms Collection):
status: New → Triaged
tags: added: audit auto-test
Adam Israel (aisrael) wrote :

I came across this while reviewing a MP for nagios and have some notes to add.

This is failing because the 100-deploy test is using precise as the default series, so the charm is being deployed to precise instead of trusty, and it depends on a package that wasn't available until trusty.

Changing the default series to trusty addresses the issue with nagios, but the test then fails with haproxy under trusty. Installing the precise version of haproxy succeeds, but then the test fails in the install hook of mysql (see

Matt Bruzek (mbruzek) wrote :

I will take a look at this and fix this problem.

Changed in nagios (Juju Charms Collection):
assignee: nobody → Matt Bruzek (mbruzek)
Charles Butler (lazypower) wrote :

In addition it appears the iterations post-facto have caused some additional issues. the monitors interface fails with the following trace:

ERROR: nagios::21-monitors-interface-test
[/tmp/bundletester-rGLciT/nagios/tests/21-monitors-interface-test exit 1]
2015-05-15 16:49:30 Starting deployment of amazon
2015-05-15 16:49:31 Deploying services...
2015-05-15 16:49:32 Deploying service mediawiki using cs:trusty/mediawiki-3
2015-05-15 16:49:39 Deploying service mysql using cs:trusty/mysql-25
2015-05-15 16:49:49 Deploying service nagios using local:trusty/nagios
2015-05-15 16:50:00 Deploying service nrpe using cs:trusty/nrpe-3
2015-05-15 16:50:08 Config specifies num units for subordinate: nrpe
2015-05-15 16:56:47 Adding relations...
2015-05-15 16:56:48 Adding relation mysql:db <-> mediawiki:db
2015-05-15 16:56:48 Adding relation nagios:monitors <-> mysql:monitors
2015-05-15 16:56:48 Adding relation nrpe:general-info <-> mysql:juju-info
2015-05-15 16:56:49 Adding relation nrpe:monitors <-> nagios:monitors
2015-05-15 16:56:49 Adding relation nrpe:local-monitors <-> mysql:local-monitors
2015-05-15 16:59:07 Exposing service 'nagios'
2015-05-15 16:59:07 Deployment complete in 576.87 seconds
Traceback (most recent call last):
  File "/tmp/bundletester-rGLciT/nagios/tests/21-monitors-interface-test", line 42, in test_nrpe_monitors_config
  File "/usr/lib/python3/dist-packages/amulet/", line 85, in file_contents
    raise IOError(output)
OSError: cat: /etc/nagios/nrpe.d/procrunning_mysqld.cfg: No such file or directory
ERROR subprocess encountered error code 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/bundletester-rGLciT/nagios/tests/21-monitors-interface-test", line 61, in <module>
  File "/tmp/bundletester-rGLciT/nagios/tests/21-monitors-interface-test", line 44, in test_nrpe_monitors_config
AttributeError: 'module' object has no attribute 'ERROR'

Cory Johns (johnsca) wrote :

Still getting test failures on this charm, and since the link to the test results in the original description is dead, here is a permanent link to the results I just got:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers