Bug 788664 - unable to push image to cloud resource provider "ec2-sa-east-1"
Summary: unable to push image to cloud resource provider "ec2-sa-east-1"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: imagefactory
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
Assignee: jrd
QA Contact: Ramesh A
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 18:16 UTC by Rehana
Modified: 2016-04-26 15:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:16:55 UTC


Attachments (Terms of Use)

Description Rehana 2012-02-08 18:16:36 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Added provider account 
2.Build an image, push the image to "ec2-us-east-1", completed successfully
3.Tried to push the same image to  "ec2-sa-east-1"account, the operation failed with the below error

Error Log(/var/log/imagefactory.log):

2012-02-08 12:50:25,064 DEBUG imgfac.ReservationManager.ReservationManager thread(7dfbd8d7) Message: ENTERING queue: (ec2)
2012-02-08 12:50:25,065 DEBUG imgfac.ReservationManager.ReservationManager thread(7dfbd8d7) Message: SUCCESS ENTERING queue: (ec2)
2012-02-08 12:50:25,065 DEBUG imgfac.BuildJob.BuildJob thread(7dfbd8d7) Message: Builder (7dfbd8d7-4af8-43a4-aea2-390b167872d2) changed status from NEW to PUSHING
2012-02-08 12:50:25,065 DEBUG imgfac.BuildJob.BuildJob thread(7dfbd8d7) Message: Builder (7dfbd8d7-4af8-43a4-aea2-390b167872d2) changed percent complete from 0 to 0
2012-02-08 12:50:25,065 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder thread(7dfbd8d7) Message: Exception caught in ImageFactory
2012-02-08 12:50:25,065 DEBUG imgfac.builders.BaseBuilder.Fedora_ec2_Builder thread(7dfbd8d7) Message: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 458, in push_image
    credentials)
  File "/usr/lib/python2.6/site-packages/imgfac/builders/Fedora_ec2_Builder.py", line 531, in push_image_snapshot_ec2
    region_conf=self.ec2_region_details[region]
KeyError: 'ec2-sa-east-1'

2012-02-08 12:50:25,065 DEBUG imgfac.BuildJob.BuildJob thread(7dfbd8d7) Message: Builder (7dfbd8d7-4af8-43a4-aea2-390b167872d2) changed status from PUSHING to FAILED
2012-02-08 12:50:25,065 DEBUG imgfac.BuildJob.BuildJob thread(7dfbd8d7) Message: 7dfbd8d7-4af8-43a4-aea2-390b167872d2 for ec2 about to exit ec2 queue...

log from /var/log/deltacloud-core/mock.log

W, [2012-02-08T12:58:19.293054 #7200]  WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
I, [2012-02-08T12:58:19.299500 #7200]  INFO -- : Opening new HTTPS connection to ec2.us-west-2.amazonaws.com:443
I, [2012-02-08T12:58:19.300912 #7200]  INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-02-08T12:58:19.302502 #7200]  INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-02-08T12:58:19.304240 #7200]  INFO -- : Closing HTTPS connection to ec2.sa-east-1.amazonaws.com:443
W, [2012-02-08T12:58:19.466541 #7200]  WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
I, [2012-02-08T12:58:19.466885 #7200]  INFO -- : Opening new HTTPS connection to ec2.us-east-1.amazonaws.com:443
I, [2012-02-08T12:58:19.473388 #7200]  INFO -- : Opening new HTTPS connection to ec2.sa-east-1.amazonaws.com:443
I, [2012-02-08T13:02:31.373499 #7200]  INFO -- : New Aws::Ec2 using per_thread-connection mode
W, [2012-02-08T13:02:31.378139 #7200]  WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
I, [2012-02-08T13:02:31.378215 #7200]  INFO -- : Opening new HTTPS connection to ec2.sa-east-1.amazonaws.com:443
I, [2012-02-08T13:03:26.676535 #7200]  INFO -- : New Aws::Ec2 using per_thread-connection mode
I, [2012-02-08T13:03:26.682492 #7200]  INFO -- : Closing HTTPS connection to ec2.sa-east-1.amazonaws.com:443

rpm package :

[root@qe-blade-06 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-23.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-conductor-daemons-0.8.0-23.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-23.el6.noarch
aeolus-all-0.8.0-23.el6.noarch

Actual results:


Expected results:


Additional info:

Comment 1 wes hayutin 2012-02-22 23:46:57 UTC
moving version to 1.0.0 .  version = found in version

Comment 3 Hugh Brock 2012-02-23 15:11:18 UTC
We should be testing pushing to all regions. Moving to ON_QA to test 'em all and get a full report.

Comment 5 Ramesh A 2012-02-23 18:46:33 UTC
Verified and able to push images to the all the mentioned regions in EC2

1. ec2-us-east-1
2. ec2-us-west-1
3. ec2-ap-southeast-1
4. ec2-eu-west-1
5. ec2-us-west-2
6. ec2-sa-east-1
7. ec2-ap-northeast-1

Comment 6 Ramesh A 2012-02-23 19:17:25 UTC
Forgot to mention the rpm details in my previous comment

[root@bigisis ~]# rpm -qa| grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
[root@bigisis ~]#


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