Description of problem: When deploying an orchestration stack, CloudForms errors out however, the stack is deployed in AWS. Version-Release number of selected component (if applicable): 5.10.5 How reproducible: always Steps to Reproduce: 1. Deploy Orchestration stack to AWS 2. 3. Actual results: CloudForms errors out Expected results: No errors in CloudForms Additional info: [----] E, [2019-11-14T08:32:01.955219 #21320:848f50] ERROR -- : Q-task_id([r6000000009985_service_template_provision_task_6000000005450]) MIQ(ManageIQ::Providers::CloudManager::OrchestrationTemplateRunner#poll_stack_status) Orchestration stack deployment error: The following resource(s) failed to create: [AccountSetup]. . Please examine stack resources for more details
https://github.com/ManageIQ/manageiq/pull/19555
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/6d1207783cdd4dffa0b176594184522b0a160ec0 commit 6d1207783cdd4dffa0b176594184522b0a160ec0 Author: Lucy Fu <lufu> AuthorDate: Thu Nov 21 09:54:16 2019 -0500 Commit: Lucy Fu <lufu> CommitDate: Thu Nov 21 09:54:16 2019 -0500 Fine tune the error handling. https://bugzilla.redhat.com/show_bug.cgi?id=1773595 app/models/manageiq/providers/cloud_manager/orchestration_template_runner.rb | 14 +- 1 file changed, 7 insertions(+), 7 deletions(-) https://github.com/ManageIQ/manageiq/commit/aff456ad25b4f764512f71b234b0e20c1a5b5f1a commit aff456ad25b4f764512f71b234b0e20c1a5b5f1a Author: Lucy Fu <lufu> AuthorDate: Thu Nov 21 10:01:05 2019 -0500 Commit: Lucy Fu <lufu> CommitDate: Thu Nov 21 10:01:05 2019 -0500 Raise an error in case the orchestration template runner finishes unexpectedly OrchestrationTemplateRunner would get into finished state when the stack already exists on the provider side. https://bugzilla.redhat.com/show_bug.cgi?id=1773595 app/models/manageiq/providers/cloud_manager/orchestration_template_runner.rb | 4 +- app/models/service_orchestration.rb | 2 + spec/models/service_orchestration_spec.rb | 7 + 3 files changed, 11 insertions(+), 2 deletions(-)
Above PR addressed the issue that the provision method didn't raise an error immediately, instead of waited 10 minutes.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days