New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/27745bc2bdd08d08c5f9c002e81d1e3d6ce4cd43 commit 27745bc2bdd08d08c5f9c002e81d1e3d6ce4cd43 Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Dec 15 14:45:51 2016 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Wed Jan 11 16:32:01 2017 -0500 Merge pull request #12347 from billfitzgerald0120/notify_vms Automate - Notification for VM Provisioning error. (cherry picked from commit 4a92243eebeef88909c7f098fa1aa2192636122b) https://bugzilla.redhat.com/show_bug.cgi?id=1412288 .../__methods__/update_provision_status.rb | 5 +++++ .../__methods__/update_provision_status.rb | 5 +++++ .../__methods__/update_provision_status.rb | 5 +++++ .../update_provision_status_vm_cloud_spec.rb | 12 ++++++++++++ .../update_provision_status_vm_infra_spec.rb | 12 ++++++++++++ .../update_provision_status_vm_template_infra_spec.rb | 12 ++++++++++++ 6 files changed, 51 insertions(+)
Verified in 5.7.1.0. I copied the instance of state machine that takes care of cloud vm provisioning from template. I modified the copied instance's class to have max retries only 1 everywhere. I then copied the preprovision method for openstack and set it to retry forever. Once I kicked the provisioning off, I received a notification in a couple of minutes starting with "VM Provision Error:" as the code in PR is supposed to do.
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/RHSA-2017-0320.html