Bug 1712595
Summary: | VM Provisioning Timeout - EMS needs manual refresh to see 'new' VMs | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Providers | Assignee: | Lucy Fu <lufu> |
Status: | CLOSED ERRATA | QA Contact: | Kedar Kulkarni <kkulkarn> |
Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | high | ||
Version: | 5.9.5 | CC: | agrare, dmetzger, jfrey, jhardy, jprause, mshriver, obarenbo, simaishi, tfitzger |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.10.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.10.5.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1696889 | Environment: | |
Last Closed: | 2019-06-11 05:32:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | VMware | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1696889 | ||
Bug Blocks: |
Comment 2
CFME Bot
2019-05-22 14:12:23 UTC
New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/5aab9040783070241ac4b5195b9212693086225d commit 5aab9040783070241ac4b5195b9212693086225d Author: Jason Frey <jfrey> AuthorDate: Tue May 21 12:31:27 2019 -0400 Commit: Jason Frey <jfrey> CommitDate: Tue May 21 12:31:27 2019 -0400 Merge pull request #18715 from lfu/src_vm_or_dest_host_1696889 Add src_vm_or_dest_host_refresh_target. (cherry picked from commit 8a87d0f3cba7f961aa02a16c19c333aaa7ae3920) https://bugzilla.redhat.com/show_bug.cgi?id=1712595 app/models/ems_event.rb | 4 + spec/models/ems_event_spec.rb | 19 + 2 files changed, 23 insertions(+) On 5.10.5.1 I was able to setup a situation where I selected Host1 for provisioning a VM on our VMware, but before provisioning request could finish, the VMware used vMotion to move the VM to Host3(using DRS). This did NOT cause any errors with refresh or service provisioning. Our Full provider refresh was not long running though as env is small, hence not exactly what customer experienced. Verified on 5.10.5.1. 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/RHSA-2019:1429 |