The nagios charm fails automated testing
Bug #1403574 reported by
Matt Bruzek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nagios (Juju Charms Collection) |
Triaged
|
Undecided
|
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 http://
The latest automated test results can be found here:
http://
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.
Changed in nagios (Juju Charms Collection): | |
status: | New → Triaged |
tags: | added: audit auto-test |
To post a comment you must log in.
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 https:/ /bugs.launchpad .net/charms/ +source/ mysql/+ bug/1408673).