Bug 1388600 - When provisioning a VM, during the status check (after the clone has completed), CloudForms throws the error "wrong number of arguments (2 for 0)"
Summary: When provisioning a VM, during the status check (after the clone has complete...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Greg Blomquist
QA Contact: Leo Khomenko
URL:
Whiteboard: provision:error
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-25 18:13 UTC by Saif Ali
Modified: 2020-01-17 16:05 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-07 16:04:20 UTC
Category: ---
Cloudforms Team: RHEVM
Target Upstream Version:


Attachments (Terms of Use)

Description Saif Ali 2016-10-25 18:13:13 UTC
Description of problem:
Provisioning was confirmed working in the test environment with CFME version 5.5.4.2-1 against RHEV 3.5. After the upgrade to 4.0 .

Version-Release number of selected component (if applicable):
5.5.5.4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Saif Ali 2016-10-25 18:14:19 UTC
[----] E, [2016-10-24T16:38:43.346701 #2899:1499c8c] ERROR -- : <RHEVM> Ovirt::Service#resource_get: class = ArgumentError, message=wrong number of arguments (2 for 0), /api/events?from=47228745
[----] E, [2016-10-24T16:38:43.346932 #2899:1499c8c] ERROR -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::EventCatcher::Runner#start_event_monitor) EMS [itw-rhevm] as [admin@internal] Event Monitor Thread aborted because [wrong number of arguments (2 for 0)]
[----] E, [2016-10-24T16:38:43.347005 #2899:1499c8c] ERROR -- : [ArgumentError]: wrong number of arguments (2 for 0)  Method:[rescue in block in start_event_monitor]
[----] E, [2016-10-24T16:38:43.347068 #2899:1499c8c] ERROR -- : /opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/abstract_response.rb:71:in `return!'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/service.rb:208:in `block in resource_verb'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:592:in `call'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:592:in `process_result'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:504:in `block in transmit'
/opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:853:in `start'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:494:in `transmit'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:202:in `execute'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/request.rb:52:in `execute'
/opt/rh/cfme-gemset/gems/rest-client-2.0.0.rc1/lib/restclient/resource.rb:51:in `get'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/service.rb:201:in `resource_verb'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/service.rb:174:in `resource_get'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/service.rb:112:in `standard_collection'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/inventory.rb:100:in `standard_collection'
/opt/rh/cfme-gemset/gems/ovirt-0.7.2/lib/ovirt/inventory.rb:31:in `events'
/var/www/miq/vmdb/gems/pending/ovirt_provider/events/ovirt_event_monitor.rb:28:in `each_batch'
/var/www/miq/vmdb/app/models/manageiq/providers/redhat/infra_manager/event_catcher/runner.rb:33:in `monitor_events'
/var/www/miq/vmdb/app/models/manageiq/providers/base_manager/event_catcher/runner.rb:116:in `block in start_event_monitor'

Comment 3 Ian Tewksbury 2016-10-26 14:58:08 UTC
This error was seen when connecting to a RHV 3.3 environment.

Wanted to be sure that was clear.

The testing was done against RHV 3.5 and then when upgrading in an environment with RHV 3.3 this error was seen.

Comment 4 Henry Grover 2016-10-26 17:57:16 UTC
This seems to be the same bug as listed in https://bugzilla.redhat.com/show_bug.cgi?id=1328087

Comment 8 Henry Grover 2016-10-27 20:23:56 UTC
An update: I've tested modifying line 208 of service.rb in the ovirt gem (on all workers) to only pass &block to the return! method over in the rest-client gem. I'm able to provision successfully sometimes now, but still have intermittent failures and frequent instances of the same error message posted above in evm.log.

I'm pretty confused by this. The stack trace seems to pretty clearly identify the ArgumentError originating from an attempt to call return! with multiple arguments, but I don't see that could be happening given that this is the only instance I can find of it being called at all, and given that I've modified the way it's being called.

Comment 9 Henry Grover 2016-10-27 22:13:37 UTC
Oh, duh, didn't restart evmserverd. After doing so, this appears to be fixed. Pretty confident this is just the bug I linked above.

Comment 25 Greg Blomquist 2017-03-07 16:04:20 UTC
This customer case was closed and as Marcel points out, this only impacts CFME 5.5 and earlier.


Note You need to log in before you can comment on or make changes to this bug.