Description of problem: If the Automate role is not defined on a server we still see the UI and dialogs making direct Automate calls and not honoring the role. The Automate calls should get routed to the correct appliance that has the role defined instead of getting directly executed on the current appliance where the UI worker is running. Version-Release number of selected component (if applicable): 5.4 How reproducible: Very Steps to Reproduce: 1. Disable the Automate Role, (default is currently to be disabled on a new appliance) 2. Run the CFME UI 3. The UI should not be able to display the Provisioning Dialogs and other dialogs that make direct Automate calls. Actual results: Expected results: Additional info:
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/92ba718d3c35f76bcd1afd4cc158b212fad553e8 commit 92ba718d3c35f76bcd1afd4cc158b212fad553e8 Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Jun 18 17:39:57 2015 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Wed Jun 24 11:55:42 2015 -0400 Automate Worker Support for adding a new Automate Worker that owns the automate queue. https://bugzilla.redhat.com/show_bug.cgi?id=1231939 vmdb/app/controllers/ops_controller/settings/common.rb | 16 ++++++++++++++++ vmdb/app/models/miq_automate_worker.rb | 10 ++++++++++ .../worker_management/monitor/class_names.rb | 2 ++ vmdb/app/views/ops/_settings_workers_tab.html.haml | 17 +++++++++++++++++ vmdb/config/vmdb.tmpl.yml | 2 ++ vmdb/lib/workers/automate_worker.rb | 4 ++++ .../icons/new/processmanager-automate_worker.png | Bin 0 -> 6882 bytes 7 files changed, 51 insertions(+) create mode 100644 vmdb/app/models/miq_automate_worker.rb create mode 100644 vmdb/lib/workers/automate_worker.rb create mode 100644 vmdb/public/images/icons/new/processmanager-automate_worker.png
https://github.com/ManageIQ/manageiq/pull/3258
https://github.com/ManageIQ/manageiq/pull/5073
Moved to assigned since this work is currently deferred.
This BZ has been closed since it was opened on a version of CloudForms that has reached the end of its lifecycle. If you find that this bug is still relevant, please open a new BZ against the relevant supported version of CloudForms.