Bug 2007384 - Failed to parse 'writeRate' value xxxx to integer: For input string: xxxx
Summary: Failed to parse 'writeRate' value xxxx to integer: For input string: xxxx
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: shani
QA Contact: sshmulev
URL:
Whiteboard:
Depends On:
Blocks: 2007550
TreeView+ depends on / blocked
 
Reported: 2021-09-23 17:49 UTC by Jaroslav Spanko
Modified: 2024-12-20 21:11 UTC (History)
10 users (show)

Fixed In Version: ovirt-engine-4.5.0.1
Doc Type: Bug Fix
Doc Text:
Previously high values of disk writeRate/readRate were not processed properly by the ovirt-engine. In this release, the type of writeRate/readRate in ovirt-engine has changed from integer to long to support values that are higher than integers.
Clone Of:
: 2007550 (view as bug list)
Environment:
Last Closed: 2022-05-26 16:23:11 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 197 0 None open Fix readRate/writeRate (long instead of int) 2022-03-28 16:01:55 UTC
Red Hat Issue Tracker RHV-43702 0 None None None 2021-09-23 17:51:39 UTC
Red Hat Product Errata RHSA-2022:4711 0 None None None 2022-05-26 16:23:42 UTC

Description Jaroslav Spanko 2021-09-23 17:49:30 UTC
Description of problem:
engine.log is flooded with following messages
-----
2021-07-24 09:20:23,033+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-73) [] Failed to parse 'writeRate' value '2649267647' to integer: For input string: "2649267647"
2021-07-25 05:31:32,021+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-38) [] Failed to parse 'readRate' value '2243888802' to integer: For input string: "2243888802"
-----

$ grep "Failed to parse" engine.log| wc -l
74256

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

How reproducible:
100% in customer environments, found during architecture reviews 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1929211 but looking to the fix only read/write ops was fixed to bigint, not write/read rate

Comment 6 Nir Soffer 2022-03-27 14:59:30 UTC
I could reproduce this with a nested environment using fio.

How to reproduce:

1. Add NFS storage domain running on the same host as the nested host, or
   in vm running on the same as the nested host.

My setup looks like this:

bare metal:
  - vm1: host1
    - test vm
  - vm2: engine
  - vm3: nfs server

2. Create test vm with an empty virtio thin disk on the nfs domain
3. Install fio in the test vm

    dnf install fio

4. Create fio file for testing

# cat seqread.fio 
[global]
size=1g
runtime=60
time_based=1
ioengine=libaio
direct=1
numjobs=4

[read]
readwrite=read
iodepth=8
blocksize=1m

5. Run fio in the test vm

# fio --filename /dev/vda seqread.fio 
read: (g=0): rw=read, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=8
...
Run status group 0 (all jobs):
   READ: bw=2144MiB/s (2248MB/s), 525MiB/s-553MiB/s (551MB/s-580MB/s), io=126GiB (135GB), run=60005-60011msec

If you don't see bw value larger than 2 GiB/s, you cannot reproduce in this environment.

6. Check engine log for errors

2022-03-27 17:40:04,727+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-28) [] Failed to parse 'readRate' value '2365514812' to integer: For input string: "2365514812"


It you don't have NFS server connected via fast enough network, it can
be easier to reproduce with local data center. Reading from local files
is faster.

Comment 10 sshmulev 2022-04-14 11:37:42 UTC
Verified successfully.

Versions:
engine-4.5.0.2-0.7.el8ev
vdsm-4.50.0.12-1.el8ev

Checked it before on a version without the fix(engine-4.4.10.6-0.1.el8ev) and could reproduce it according to Nir's steps.
Did the same steps on the new version mentioned above and it didn't reproduce - (tried to run it 5 times).

Comment 15 errata-xmlrpc 2022-05-26 16:23:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4711

Comment 16 meital avital 2022-08-03 11:32:44 UTC
Due to QE capacity, we are not going to cover this issue in our automation


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