Tests depend on AWS_ACCESS_KEY_ID being set

Bug #819329 reported by Gustavo Niemeyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Medium
Clint Byrum
juju (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

[ERROR]
Traceback (most recent call last):
  File "/home/niemeyer/src/ensemble-bzr/trunk/ensemble/lib/mocker.py", line 146, in test_method_wrapper
    result = test_method()
  File "/home/niemeyer/src/ensemble-bzr/trunk/ensemble/environment/tests/test_config.py", line 512, in test_ec2_verifies_region
    data = self.config.get_default().get_serialization_data()
  File "/home/niemeyer/src/ensemble-bzr/trunk/ensemble/environment/environment.py", line 18, in get_serialization_data
    provider = self.get_machine_provider()
  File "/home/niemeyer/src/ensemble-bzr/trunk/ensemble/environment/environment.py", line 38, in get_machine_provider
    self._name, self._environment_config)
  File "/home/niemeyer/src/ensemble-bzr/trunk/ensemble/providers/ec2/__init__.py", line 39, in __init__
    s3_uri=config.get("s3-uri", ""))
  File "/usr/lib/pymodules/python2.7/txaws/service.py", line 102, in __init__
    creds = AWSCredentials(access_key, secret_key)
  File "/usr/lib/pymodules/python2.7/txaws/credentials.py", line 34, in __init__
    raise ValueError("Could not find %s" % ENV_ACCESS_KEY)
exceptions.ValueError: Could not find AWS_ACCESS_KEY_ID

ensemble.environment.tests.test_config.EnvironmentsConfigTest.test_ec2_verifies_region

Related branches

Changed in ensemble:
status: New → Confirmed
milestone: none → dublin
Changed in ensemble:
importance: Undecided → Medium
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

FYI, this is the only test that still fails when building inside a clean chroot.

Changed in ensemble (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Changed in ensemble:
milestone: dublin → none
Changed in ensemble:
milestone: none → eureka
status: Confirmed → In Progress
assignee: nobody → Clint Byrum (clint-fewbar)
Changed in ensemble (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

afaik this has been addressed in the relevant unit tests by setting up a proper env

Changed in juju:
status: In Progress → Fix Released
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

redirecting from ensemble to juju, and re-opening as the upstream fix is better than the patch that has been carried.

affects: ensemble (Ubuntu) → juju (Ubuntu)
Changed in juju (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju - 0.5+bzr531-0ubuntu1

---------------
juju (0.5+bzr531-0ubuntu1) precise; urgency=low

  * New upstream snapshot (LP: #985249)
  * d/p/fix-tests-without-aws-key.patch: Dropped as it has been
    superseded by a better upstream fix (LP: #819329)
  * d/p/no-write-sample-on-help.patch: Dropped, Applied upstream.
  * d/p/disable-failing-zookeeper-test.patch refreshed.
  * d/control: new code requires latest txzookeeper upstream.
 -- Clint Byrum <email address hidden> Wed, 18 Apr 2012 15:45:34 -0700

Changed in juju (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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