Bug 1670340 - Evacuate instance failed and throws an error message
Summary: Evacuate instance failed and throws an error message
Keywords:
Status: CLOSED DUPLICATE of bug 1658480
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-29 10:45 UTC by Jad Haj Yahya
Modified: 2019-07-27 02:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-31 19:03:54 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (144.11 KB, image/png)
2019-01-29 10:45 UTC, Jad Haj Yahya
no flags Details
log (207.71 KB, text/plain)
2019-01-29 10:58 UTC, Jad Haj Yahya
no flags Details

Description Jad Haj Yahya 2019-01-29 10:45:25 UTC
Created attachment 1524560 [details]
screenshot

Description of problem:
Evacuate instance failed and throws an error message

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

How reproducible:


Steps to Reproduce:
1. Create an instance
2. Shutdown server where instance is hosted
3. Go to instance summary page
4. Click Life cycle > Evacuate Instance

Actual results:
Error message thrown and process failed (see attachment)

Expected results:
Evacuation to complete successfully.

Additional info:

Comment 2 Jad Haj Yahya 2019-01-29 10:58:56 UTC
Created attachment 1524561 [details]
log

Comment 4 Marek Aufart 2019-01-29 14:16:37 UTC
This seems to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1658480 (fix was merged yesterday).

Comment 5 dmetzger 2019-01-31 19:03:54 UTC

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


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