| Summary: | When provisioning a VM, during the status check (after the clone has completed), CloudForms throws the error "wrong number of arguments (2 for 0)" | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Saif Ali <saali> |
| Component: | Providers | Assignee: | Greg Blomquist <gblomqui> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Leo Khomenko <lkhomenk> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5.0 | CC: | awestbro, cwyatt, dajohnso, gblomqui, itewksbu, jfrey, jhardy, juan.hernandez, obarenbo, saali |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | provision:error | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-07 16:04:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | RHEVM | Target Upstream Version: | |
|
Description
Saif Ali
2016-10-25 18:13:13 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' 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. This seems to be the same bug as listed in https://bugzilla.redhat.com/show_bug.cgi?id=1328087 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. Oh, duh, didn't restart evmserverd. After doing so, this appears to be fixed. Pretty confident this is just the bug I linked above. This customer case was closed and as Marcel points out, this only impacts CFME 5.5 and earlier. |