New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/18c297248587c32cbab358442a181f579a235923

commit 18c297248587c32cbab358442a181f579a235923
Author:     Greg McCullough <gmccullo>
AuthorDate: Fri Dec 2 08:09:47 2016 -0500
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Fri Dec 2 11:47:19 2016 -0500

    Merge pull request #12930 from carbonin/scope_dialog_label_validation_by_region
    
    Scope the dialog label uniqueness validation by region
    (cherry picked from commit 531a50e6c0ecd99a63ea24028292d5484fe64366)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1401014

 app/models/dialog.rb                   | 2 +-
 app/models/resource_action_workflow.rb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

You should not be creating anything in the global region when verifying this issue.

There should be two remote regions (1 and 2, for example) replicating to the global region (99). Central admin should be enabled for the two remote regions.

Then a service and dialog should be created in each of the remote regions. The dialogs should have the same name in each region.

Then, ordering one of those services from the global region would fail silently, but should now succeed.

So I should have been more clear in the initial bug description.

The issue was that the requests were never being created in the remote region.

If we see requests getting created when the dialogs have duplicated names then I would call this verified regardless of whether the requests complete successfully or not.

this BZ is verified - Request gets created.
preparing a new BZ for failing request if ordered from Global region in such setup