Bug 725457 - provider account for ec2-us-west but can push to ec2-us-east
Summary: provider account for ec2-us-west but can push to ec2-us-east
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: rubygem-aeolus-image
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
Assignee: Martyn Taylor
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-25 14:39 UTC by Dave Johnson
Modified: 2012-05-15 19:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 19:40:50 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0592 0 normal SHIPPED_LIVE new packages: rubygem-aeolus-image 2012-05-15 22:31:14 UTC

Description Dave Johnson 2011-07-25 14:39:23 UTC
Description of problem:
=========================
aeolus-image doesn't seem to check that the provider given in the push command has a valid provider account associated with it.

When I did a fresh install, added a provider account for ec2-us-west, I built a image and was able push it into ec2-us-east without error.  I don;t believe that should be the case.

Comment 1 wes hayutin 2011-09-28 16:40:04 UTC
making sure all the bugs are at the right version for future queries

Comment 3 Martyn Taylor 2011-10-06 12:24:48 UTC
This will go away in the next release when we update aeolus0image to talk directly to the new Image Management API

Comment 4 Brad P. Crochet 2011-11-07 19:05:24 UTC
Verified.

aeolus-image push now requires provider and account parameters.

[root@qeblade33 ~]# aeolus-image push --provider ec2-us-east-1 --image 6444fc75-713d-4d57-bac4-aae66a2cbf0f --build 3ccdd109-9f0f-4598-9cfa-06187acb5923 --targetimage 7957dd70-ad2c-4777-87c5-ce644df8d27cUnable to perform task: 
- Internal Error: undefined method `empty?' for nil:NilClass


* Will file a separate bug for more user-friendly output upon error

Comment 6 errata-xmlrpc 2012-05-15 19:40:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0592.html


Note You need to log in before you can comment on or make changes to this bug.