The owncloud charm fails automated testing

Bug #1403580 reported by Matt Bruzek on 2014-12-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
owncloud (Juju Charms Collection)
Status tracked in Precise
Precise
High
José Antonio Rey
Trusty
High
José Antonio Rey

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://reports.vapour.ws/charm-tests-by-charm this charm is failing automated testing.

The latest test results for owncloud can be found here:
http://reports.vapour.ws/charm-tests/charm-bundle-test-10515-results

It looks like some of the deployments were complete but there was still an environment standup timeout error message for all environments.

Also the LXC environment had the following output:
2014-12-02 19:01:10 The following units had errors:
   unit: owncloud/0: machine: 3 agent-state: error details: hook failed: "install"

Please investigate and fix the charm or fix the tests so owncloud passes automated testing. Thank you.

Related branches

José Antonio Rey (jose) on 2015-01-12
Changed in owncloud (Juju Charms Collection):
status: New → In Progress
Charles Butler (lazypower) wrote :

I've found som eissues with the test that appear to be related to the NFS relationship testing.

http://paste.ubuntu.com/9733379/

Following removal of the NFS relatioship testing from the tests - it fails in a different way of not being able to validate the webhead.

This leads me to beleive these tests are candidates for additional refactoring and update/triage. My proposed path to landing a resolution for this would be as follows:

Gut the NFS relationship tests, and fix the python-requests tests first, so we have a good baseline that we know works.

Then re-introduce the NFS relationship tests, and run the relationship cycle to examine which end of the charm series is responsible for the failure, and patch as needed.

</ my 2 cents>

José Antonio Rey (jose) on 2015-01-15
Changed in owncloud (Charms Trusty):
status: New → Triaged
Changed in owncloud (Charms Precise):
status: In Progress → Fix Committed
assignee: nobody → José Antonio Rey (jose)
importance: Undecided → High
Changed in owncloud (Charms Trusty):
importance: Undecided → High
assignee: nobody → José Antonio Rey (jose)
José Antonio Rey (jose) on 2015-01-15
Changed in owncloud (Charms Trusty):
status: Triaged → In Progress
José Antonio Rey (jose) on 2015-01-15
Changed in owncloud (Charms Trusty):
status: In Progress → Fix Committed
Antonio Rosales (arosales) wrote :

It appears work is underway to resolve testing failures:
lp:~jose/charms/precise/owncloud/fix-tests

Thus, this bug will not be moved into the unmaintained namespace of the charm store per:
 https://jujucharms.com/docs/charm-unmaintained-process
 https://lists.ubuntu.com/archives/juju/2014-December/004736.html

Thanks for working to resolve this issues, lets try to get this charm backing into a passing state asap.
-Antonio

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

Other bug subscribers