Bug 1300794 - ems_refresh errors out with "invoking [on_error] method=[update_provision_status(status => '[No Cloud/Infrastructure Provider defined]" [NEEDINFO]
Summary: ems_refresh errors out with "invoking [on_error] method=[update_provision_sta...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: GA
: 5.5.4
Assignee: Jason Frey
QA Contact: Aziza Karol
URL:
Whiteboard:
Depends On: 1297101
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-21 17:48 UTC by Satoe Imaishi
Modified: 2019-09-12 09:48 UTC (History)
9 users (show)

Fixed In Version: 5.5.4.0
Doc Type: Bug Fix
Doc Text:
Previously, when a virtual machine moved to another host during a host-targeted External Management System (EMS) refresh, the virtual machine appeared to be deleted from the host. This occurred because the EMS refresh process (ems_refresh) disconnected the virtual machine and deleted it from the EMS, resulting in this error message: "invoking [on_error] method=[update_provision_status(status => '[No Cloud/Infrastructure Provider defined]". The issue has been fixed in the code by queueing a targeted refresh on a virtual machine when there is insufficient information available. As a result, virtual machines are no longer deleted by the host EMS, and ems_refresh completes for both the host and the virtual machine.
Clone Of: 1297101
Environment:
Last Closed: 2016-05-31 13:40:39 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
jprause: needinfo? (jfrey)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1101 0 normal SHIPPED_LIVE CFME 5.5.4 bug fixes and enhancement update 2016-05-31 17:40:10 UTC

Comment 7 Aziza Karol 2016-05-05 14:26:15 UTC
No Error when a VM is migrated to another host. VM refresh successful.

Verified:5.5.4.0.20160426160942_629f93b

Comment 9 errata-xmlrpc 2016-05-31 13:40:39 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://access.redhat.com/errata/RHBA-2016:1101


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