Created attachment 1232281 [details] snapshot Description of problem: Version-Release number of selected component (if applicable): 5.7.0.16.20161213213754_1ad3545 How reproducible: 100% Steps to Reproduce: 1.Login to ssui 2.provision service 3.Navigate to the my services and click on "Open a HTML5 console for this vm" icon of that service. Actual results: see attached screenshot. "Error: [wrong number of arguments (given 2, expected 3)]" is thrown in evm.log Expected results: Additional info: evm.log [----] I, [2016-12-15T11:31:56.273067 #2876:95513c] INFO -- : MIQ(MiqQueue#deliver) Message id: [28491], Delivering... [----] E, [2016-12-15T11:31:56.276210 #2876:95513c] ERROR -- : MIQ(MiqQueue#deliver) Message id: [28491], Error: [wrong number of arguments (given 2, expected 3)] [----] E, [2016-12-15T11:31:56.276382 #2876:95513c] ERROR -- : [ArgumentError]: wrong number of arguments (given 2, expected 3) Method:[rescue in deliver] [----] E, [2016-12-15T11:31:56.276444 #2876:95513c] ERROR -- : /var/www/miq/vmdb/app/models/manageiq/providers/vmware/infra_manager/vm/remote_console.rb:15:in `remote_console_acquire_ticket' /var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:91:in `block in timeout' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `block in catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:106:in `timeout' /var/www/miq/vmdb/app/models/miq_queue.rb:343:in `deliver' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:106:in `deliver_queue_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:134:in `deliver_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:152:in `block in do_work' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `loop' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:146:in `do_work' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:334:in `block in do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:153:in `run' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:128:in `start' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:21:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:343:in `block in start' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /var/www/miq/vmdb/app/models/miq_worker.rb:341:in `start' /var/www/miq/vmdb/app/models/miq_worker.rb:270:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `times' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:52:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server.rb:158:in `start' /var/www/miq/vmdb/app/models/miq_server.rb:249:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:92:in `start' /var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>' [----] I, [2016-12-15T11:31:56.276554 #2876:95513c] INFO -- : MIQ(MiqQueue#delivered) Message id: [28491], State: [error], Delivered in [0.003490272] seconds [----] I, [2016-12-15T11:31:56.277552 #2876:95513c] INFO -- : MIQ(MiqQueue#m_callback) Message id: [28491], Invoking Callback with args: ["Finished", "error", "wrong number of arguments (given 2, expected 3)", "nil"] [----] I, [2016-12-15T11:31:56.277969 #2876:95513c] INFO -- : MIQ(MiqTask#update_status) Task: [7] [Finished] [Error] [wrong number of arguments (given 2, expected 3)] [----] I, [2016-12-15T11:31:58.088007 #5415:95513c] INFO -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::EventCatcher::Runner#filtered?) EMS [10.8.58.22] as [root] Skipping caught event [UserLogoutSessionEvent] chainId [29935318] [----] I, [2016-12-15T11:31:58.799480 #2666:95513c] INFO -- : MIQ(MiqServer#heartbeat) Heartbeat [2016-12-15 16:31:58 UTC]... [----] I, [2016-12-15T11:31:58.810899 #2666:95513c] INFO -- : MIQ(MiqServer#heartb
Can't tell at quick glance if this is backend or front-end (log like like it would be a backend issue) Josh - Can you please check the backend first, and then assign to Allen if you think it is Front-end?
I believe this is due to the change in the number of arguments passed to the `#remote_console_acquire_ticket` when invoked through the API. The expected argument count was changed in https://github.com/ManageIQ/manageiq/pull/11273. The corresponding API invoker https://github.com/ManageIQ/manageiq/blob/master/app/controllers/api/vms_controller.rb#L401 should also be changed to match the argument list. Working on a fix now.
https://github.com/ManageIQ/manageiq/pull/13212
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/31319c07ed479a3dd3ae4aed28701cd49016e3ae commit 31319c07ed479a3dd3ae4aed28701cd49016e3ae Author: Josh Langholtz <jjlangholtz> AuthorDate: Thu Dec 15 15:14:52 2016 -0500 Commit: Josh Langholtz <jjlangholtz> CommitDate: Thu Dec 15 15:35:16 2016 -0500 Update argument count for console requests through API Attempting to open an HTML5 console through the SUI does not work due to a wrong number of arguments error server-side. This change updates the enqueue to pass the correct arguments for the API controller and for the openstack provider. The other providers already have the correct number of arguments. https://bugzilla.redhat.com/show_bug.cgi?id=1405143 app/controllers/api/vms_controller.rb | 2 +- .../manageiq/providers/openstack/cloud_manager/vm/remote_console.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Environment: CFME version Downstream58z Actions Performed: Created a service through ssui and a VM was provisioned. Clicked on Access-> Open VM Console. Results: Did not see any errors popping up, new tab opened with console.