New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili:
Author: Dan Clarizio <firstname.lastname@example.org>
AuthorDate: Wed Mar 14 17:42:22 2018 -0400
Commit: Dan Clarizio <email@example.com>
CommitDate: Wed Mar 14 17:42:22 2018 -0400
Merge pull request #3562 from h-kataria/add_max_retries_for_instances
Added Max Retries text field on Instance screen
(cherry picked from commit 81d2462db09f354460390d384af6f6948ef6545e)
app/controllers/miq_ae_class_controller.rb | 2 +-
app/helpers/miq_ae_class_helper.rb | 4 +
app/views/miq_ae_class/_instance_fields.html.haml | 34 +-
app/views/miq_ae_class/_instance_form.html.haml | 66 +-
4 files changed, 68 insertions(+), 38 deletions(-)
Created attachment 1472097 [details]
I can confirm max_retries at instance level in StateMachines UI.
Rechecked it by executing state machine via simulation.
1. Created domain and class
2. Created `meth1` method and `meth1_instance` instance in class
3. Created state machine, added instance there and pointed value to `meth1_instance`
4. Added max_retries value as 3 in instance and 2 in class
5. In simulation, used `Call_Instance` with namespace, class and instance with Attribute/Value Pairs.
After submiting request we got three retries, which was what we were expected.
Found features works very well, great work folks!
Verified on: 188.8.131.52.20180726225200_f44ec83
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.