Juju Charms Collection
nfs package

The nfs charm fails automated testing

Bug #1399328 reported by Matt Bruzek
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nfs (Juju Charms Collection)
Status tracked in Precise
Precise
Triaged
Undecided
Unassigned
Trusty
Triaged
Undecided
Unassigned

Bug Description

According to the latest test results by charm http://reports.vapour.ws/charm-tests-by-charm this charm is failing automated testing.

http://reports.vapour.ws/charm-tests/charm-bundle-test-1096-results

The nfs charm fails 00-setup, and 100-deploy in the automated tests.

00-setup output:
Error: must run as root
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

100-deploy output:
2014-09-26 19:42:29 Config specifies num units for subordinate: owncloud-sentry
2014-09-26 19:45:42 The following units had errors:
   unit: owncloud/1: machine: 3 agent-state: error details: hook failed: "install"

José Antonio Rey (jose)
Changed in nfs (Juju Charms Collection):
status: New → Triaged
Revision history for this message
Matt Bruzek (mbruzek) wrote :

The trusty version of the nfs charm also fails automated testing.

The latest automated test output for trusty can be found here:
http://reports.vapour.ws/charm-tests/charm-bundle-test-4988-results

The output for HP cloud is :

2014-11-04 03:56:58 Deployment complete in 484.21 seconds
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/charm-bundle-test/tmp7HVezN/nfs/tests/100-deploy", line 66, in <module>
    file_test = sentries['nfs'].file('/srv/data/relation-sentry/amulet-file-test')
  File "/usr/lib/python3/dist-packages/amulet/sentry.py", line 22, in file
    return self.file_stat(filename)
  File "/usr/lib/python3/dist-packages/amulet/sentry.py", line 77, in file_stat
    return self._fs_data(filename)
  File "/usr/lib/python3/dist-packages/amulet/sentry.py", line 74, in _fs_data
    return self._run_unit_script("filesystem_data.py {}".format(path))
  File "/usr/lib/python3/dist-packages/amulet/sentry.py", line 114, in _run_unit_script
    raise IOError(output)
OSError: Traceback (most recent call last):
  File "/tmp/amulet/filesystem_data.py", line 7, in <module>
    s = os.stat(sys.argv[1])
OSError: [Errno 2] No such file or directory: '/srv/data/relation-sentry/amulet-file-test'
ERROR subprocess encountered error code 1

Please consider fixing the charm or the tests so this charm passes automated testing.

Changed in nfs (Charms Trusty):
status: New → Triaged
Revision history for this message
Antonio Rosales (arosales) wrote :

Updated maintainer email address needed.

tags: added: maintainer-needed
Revision history for this message
Antonio Rosales (arosales) wrote :

This bug was marked as an unmaintained charm per Unmaintained Charm Policy[0]. Per the process this bug was filled, email[1] sent to the community, and email sent to the maintainer. As there have been no updates this bug report, or merge proposals to bring this charm back into a working state this charm will be moved into the un-maintained namespace of the Charm Store. The charm will still be available in the Charm Store, but not under the recommended name space as it is failing deployment and Charm Policy[2]. Anyone can at anytime work on this charm, bring it back to passing Charm Policy[2], and resubmit[3] it as a recommended Charm.

[0] https://jujucharms.com/docs/charm-unmaintained-process
[1] https://lists.ubuntu.com/archives/juju/2014-December/004736.html
[2] https://jujucharms.com/docs/authors-charm-policy
[3] https://jujucharms.com/docs/authors-charm-store#submitting

tags: added: unmaintained
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.