Bug 1190225 - VM migrate error with Class [unknown/VM/Lifecycle] not found in MiqAeDatastore
Summary: VM migrate error with Class [unknown/VM/Lifecycle] not found in MiqAeDatastore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.3.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: 5.3.4
Assignee: Tina Fitzgerald
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On: 1174881
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-06 17:22 UTC by Tina Fitzgerald
Modified: 2019-07-11 08:37 UTC (History)
12 users (show)

Fixed In Version: 5.3.4.1
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, virtual machine migrations used to fail with the error that the Parse_provider_category method could not parse the vm_migrate_request object information. This was due to missing virtual machine migrate state machine path information. This bug was fixed by adding the missing path information. Virtual machine migrations now works as expected in the new version of CloudForms Management Engine.
Clone Of: 1174881
Environment:
Last Closed: 2015-04-29 13:18:59 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1433443 0 None None None Never
Red Hat Product Errata RHBA-2015:0890 0 normal SHIPPED_LIVE cfme (5.3.4) bug fix and enhancement update 2015-04-29 17:18:32 UTC

Comment 3 Pete Savage 2015-04-21 17:56:20 UTC 
Verified in 5.3.4.2.20150415125246
Comment 5 errata-xmlrpc 2015-04-29 13:18:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0890.html
Note You need to log in before you can comment on or make changes to this bug.