Bug 1380367 - AWS provisioning occasionally fails with error The instance ID '$ID' does not exist
Summary: AWS provisioning occasionally fails with error The instance ID '$ID' does not...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: GA
: 5.7.0
Assignee: Drew Bomhof
QA Contact: Matouš Mojžíš
URL:
Whiteboard: provision:ec2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-29 11:55 UTC by Matouš Mojžíš
Modified: 2017-12-22 14:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-13 17:32:40 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
evm.log (6.67 KB, text/plain)
2016-09-29 11:55 UTC, Matouš Mojžíš 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Matouš Mojžíš 2016-09-29 11:55:05 UTC 
Created attachment 1205937 [details]
evm.log

Description of problem:


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

How reproducible:
5%

Steps to Reproduce:
1.Add an ec2 provider
2.Provision an instance
3.

Actual results:
Error added as attachment

Expected results:


Additional info:
Comment 2 Greg McCullough 2016-09-29 13:21:53 UTC 
Drew - I recall hearing about this recently but this
Comment 3 Greg McCullough 2016-09-29 13:21:54 UTC 
Drew - I recall hearing about this recently but this
Comment 4 Greg McCullough 2016-09-29 13:24:40 UTC 
(In reply to Greg McCullough from comment #3)
> Drew - I recall hearing about this recently but this

As in the middle of editing when I updated the Summary and this got saved.  :)


Drew - I recall hearing about this recently (cannot remember who, maybe Tina) but this is the first time it is being reported.  Need to look into the error and will probably need to work with someone on the providers team.
Note You need to log in before you can comment on or make changes to this bug.