Bug 1300794
| Summary: | ems_refresh errors out with "invoking [on_error] method=[update_provision_status(status => '[No Cloud/Infrastructure Provider defined]" | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Providers | Assignee: | Jason Frey <jfrey> |
| Status: | CLOSED ERRATA | QA Contact: | Aziza Karol <akarol> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.4.0 | CC: | cpelland, jfrey, jhardy, jprause, jrafanie, mfeifer, mkanoor, obarenbo, tfitzger |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.5.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1297101 | Environment: | |
| Last Closed: | 2016-05-31 13:40:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1297101 | ||
| Bug Blocks: | |||
|
Comment 7
Aziza Karol
2016-05-05 14:26:15 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |