Created attachment 1085790 [details] err Description of problem: Version-Release number of selected component (if applicable): 5.5.0.7 How reproducible: 100% Steps to Reproduce: 1.create a catalog item to deploy heat stack for openstack provider 2.order the service Actual results: "Eror during 'Provisioning': undefined method `match' for 2:Fixnum" displayed in UI. see attached screenshot. Expected results: should be able to provision Additional info:
https://github.com/ManageIQ/manageiq/pull/5127
The timeout textfield is numeric type which does not and cannot have regular expression validator. The regular expression validator is removed by the following PR. https://github.com/ManageIQ/manageiq/pull/5127 Any new service dialog created from an orchestration template using our automatic tool should no longer have this problem after this fix. To fix the problem for an existing dialog, one should go to Automate/Customization/Dialog and manually edit the dialog: 1. Identify the dialog to be edited. 2. Select Timeout textfield 3. Change Validator Type to None 4. Clear Validate Rule 5. Save
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/5d3ca6b522cf688c2a65a4af994a5da9b3ead781 commit 5d3ca6b522cf688c2a65a4af994a5da9b3ead781 Author: Bill Wei <bilwei> AuthorDate: Mon Oct 26 15:16:28 2015 -0400 Commit: Bill Wei <bilwei> CommitDate: Mon Oct 26 15:27:18 2015 -0400 Remove regex validator for timeout text field Timeout text field is integer type that does not need a regex validator https://bugzilla.redhat.com/show_bug.cgi?id=1274673 app/services/orchestration_template_dialog_service.rb | 2 -- spec/services/orchestration_template_dialog_service_spec.rb | 2 +- 2 files changed, 1 insertion(+), 3 deletions(-)
Heat stack deployment successful. Verified: 5.5.0.9-beta2.20151102161742_5530c9a
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