Bug #13091


rbovirt times out when listing VMs in RHEV compute resource

Added by Bryan Kearney almost 8 years ago. Updated over 5 years ago.

Compute resources - oVirt
Target version:
Fixed in Releases:
Found in Releases:


Cloned from
Description of problem:
Timeout when trying to list the VMs in a RHEV compute resource.

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

How reproducible:

Steps to Reproduce:
1. Add a RHEV compute resource with a large number of VMs
2. Try to view the list of VMs in the RHEV compute resource

Actual results:
- Web ui displays "There was an error listing VMs: Request Timeout".

- /var/log/foreman/production.log shows the request is timing out after 60 seconds:

2015-12-29 09:29:00 [D] RestClient.get "", "Accept"=>"application/xml", "Accept-Encoding"=>"gzip, deflate", "Authorization"=>"Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "Content-Type"=>"application/xml"

2015-12-29 09:29:00 [D] # => 200 OK | application/xml 379 bytes

2015-12-29 09:29:00 [D] RestClient.get "", "Accept"=>"application/xml; detail=disks; detail=nics; detail=hosts", "Accept-Encoding"=>"gzip, deflate", "Authorization"=>"Basic xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "Content-Type"=>"application/xml"

2015-12-29 09:30:01 [W] Error has occurred while listing VMs on RHEV-DC (RHEV): Request Timeout

Expected results:
The VMs are listed.

Additional info:
rbovirt seems to be inheriting the default timeout from Net::HTTP .
In file /usr/share/ruby/net/http.rb:

630     # Creates a new Net::HTTP object for the specified server address,
631 # without opening the TCP connection or initializing the HTTP session.
633     def initialize(address, port = nil)
645       @read_timeout = 60
Actions #1

Updated by Dominic Cleal almost 8 years ago

  • Subject changed from rbovirt: sat6 times out when listing VMs in RHEV compute resource to rbovirt times out when listing VMs in RHEV compute resource
  • Category changed from Compute resources to Compute resources - oVirt
  • Priority changed from High to Normal
Actions #2

Updated by Ohad Levy almost 8 years ago

rhev by default does not paginate, it is possible to force pagination by using the max attribute, see

however, in order to use it with datatables, we would need to support passing pagination information via the compute resource vms controller, and respond with json instead.

Actions #3

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Tomer Brisker
  • Pull request added
Actions #4

Updated by Anonymous over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release set to 136

Also available in: Atom PDF