Bug 1475774 - RHV-M requesting four GetDeviceListVDSCommand when editing storage domain
RHV-M requesting four GetDeviceListVDSCommand when editing storage domain
Status: NEW
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
All Linux
unspecified Severity medium
: ovirt-4.3.0
: ---
Assigned To: Fred Rolland
: Performance
Depends On: 1259353
  Show dependency treegraph
Reported: 2017-07-27 06:22 EDT by nijin ashok
Modified: 2018-05-10 17:44 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3132211 None None None 2017-07-31 01:47 EDT

  None (edit)
Description nijin ashok 2017-07-27 06:22:15 EDT
Description of problem:

When we click on Manage domain , RHV-M is requesting 4 GetDeviceListVDSCommand with same arguments on the same host. The whole process can take around 1-2 minute in an environment with large number of LUNs.

For the customer, it was taking around 90 seconds in a host which is having 181 LUNs. Each GetDeviceListVDSCommand was taking around 15-20 seconds (Expected with large number of LUNs). The customer is using RHEV 3.6 and I can see 6  GetDeviceListVDSCommand however it's reduced to 4 in 4.1. 

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

RHV 4.1

How reproducible:


Steps to Reproduce:

1. Click on manage storage domain and find the GetDeviceListVDSCommand executed in the engine log.

Actual results:

Editing storage domain can take some time to show up if the host is having large number of LUNs.

Expected results:

If all the calls are same, issue only 1 call while clicking edit storage domain.

Additional info:

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