Bug 768113
Summary: | Deleting deployment fails for ec2 instances when the provider account is not named "ec2" | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | Greg Blomquist <gblomqui> |
Component: | aeolus-conductor | Assignee: | Greg Blomquist <gblomqui> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0.0 | CC: | akarol, deltacloud-maint, redakkan, ssachdev |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Greg Blomquist
2011-12-15 19:27:57 UTC
QE.. is this still an issue? I have tried to create the same scenario, created EC2 provider account with the same name: "rhcloud@ec2" ,launched an application on the provider. I was able to Delete the stopped application on the EC2 provider, with out any issue. So moving the status to verified. on: rpm -qa | grep aeolus aeolus-conductor-doc-0.8.9-1.el6.noarch aeolus-configure-2.5.3-1.el6.noarch aeolus-conductor-0.8.9-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.8.9-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-daemons-0.8.9-1.el6.noarch |