New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/71f3586d315408f9d8dd30d9c44555a8acdc0b78 commit 71f3586d315408f9d8dd30d9c44555a8acdc0b78 Author: Brandon Dunne <brandondunne> AuthorDate: Mon Mar 4 11:27:26 2019 -0500 Commit: Brandon Dunne <brandondunne> CommitDate: Mon Mar 4 11:27:26 2019 -0500 Merge pull request #18511 from d-m-u/fixing_service_task_type Fix the dynamic service task naming generation for subclasses (cherry picked from commit 7870b3faeb1c649f79a7100b3a7b1007b2327cfa) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1685737 app/models/service_retire_task.rb | 12 +- spec/models/service_retire_task_spec.rb | 56 +- 2 files changed, 49 insertions(+), 19 deletions(-)
Sure Niyaz. So for provisioning bundles it's best if you start with successful item provisioning. So once you have service item provisions without errors you can build the bundle with those items. Could you please try that?
That will require the service items 1) to all have dialogs already and 2) to have display set to true.
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/RHBA-2019:0694