Description of problem: Both AWS and OpenStack takes the timeout parameter in minutes. Currently the auto generated dialog takes the timeout in seconds. Also the provisioning of AWS stack passes the number of seconds literally as number of minutes which is wrong. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/3095
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/ec4d692d75d7c644db3d7684da03b82ffd1edd52 commit ec4d692d75d7c644db3d7684da03b82ffd1edd52 Author: Bill Wei <bilwei> AuthorDate: Mon Jun 8 13:47:07 2015 -0400 Commit: Bill Wei <bilwei> CommitDate: Mon Jun 8 13:47:07 2015 -0400 orchestration provisioning timeout should be in minutes https://bugzilla.redhat.com/show_bug.cgi?id=1229380 vmdb/app/models/service_orchestration/option_converter_openstack.rb | 2 +- vmdb/app/services/orchestration_template_dialog_service.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Minutes were passed to HEAT in an openstack orchestration template provision Verified in 5.5.0.11
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-2015:2551