The owncloud charm fails automated testing
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| owncloud (Juju Charms Collection) | Status tracked in Precise | |||||
| Precise |
Fix Committed
|
High
|
José Antonio Rey | |||
| Trusty |
Fix Committed
|
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://
The latest test results for owncloud can be found here:
http://
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
- Charles Butler (community): Needs Fixing
- Review Queue (community): Needs Fixing (automated testing)
-
Diff: 100 lines (+13/-46)1 file modifiedtests/100-deploy.py (+13/-46)
| Changed in owncloud (Juju Charms Collection): | |
| status: | New → In Progress |
| Charles Butler (lazypower) wrote | #1 |
| 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) |
| Changed in owncloud (Charms Trusty): | |
| status: | Triaged → In Progress |
| Changed in owncloud (Charms Trusty): | |
| status: | In Progress → Fix Committed |
| Antonio Rosales (arosales) wrote | #2 |
I've found som eissues with the test that appear to be related to the NFS relationship testing.
http://
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>