Bug 726428

Summary:	[DOC]: ec2 push failure when deleting temporary security group
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	Documentation	Assignee:	Steve Loranz <sloranz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dave Johnson <dajohnso>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.3.1	CC:	cpelland, deltacloud-maint, jclift, nobody, whayutin
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-19 20:35:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Johnson 2011-07-28 14:57:21 UTC

Description of problem:
===============================
Over the past few days, more and more ec2 pushes are starting to fail (seen in the logs and qpid bus) because it is taking longer than usual to delete the temporary security group created for the push process.

The pushed image will still deploy when this error is encountered.  We need to document this in the release notes directing the user to manually delete the temporary security group named "imagefactory-<uuid>" when no other pushes are in progress.

See bug 726203 for more information

Comment 1 Dave Johnson 2011-07-28 17:29:04 UTC

We also need to specify that in order for the image deploy to work, the deployment xml needs to specify both the image id and the build id like so:

<assembly name="foo" hwp="hwp1">
    <image id="bebf7d02-b7a4-4448-8671-18e096e2d20e" build="b63324d7-4153-4369-a13c-569c1193f20c">
</image>

Comment 2 wes hayutin 2011-08-19 15:14:28 UTC

fixed in..
Add progress to the image warehouse upload code. 

Chris Lalancette (author)
2 days ago
commit  9203de55dc6d9114db1f
tree    f3e31986142832f138d0
parent  069705c0e6518e7a60f5

Comment 3 wes hayutin 2011-08-30 19:58:13 UTC

think this is fixed in the latest factory

Comment 4 Steve Loranz 2011-09-19 20:35:49 UTC


*** This bug has been marked as a duplicate of bug 726203 ***

Comment 5 wes hayutin 2011-12-08 13:48:51 UTC

perm close