Description of problem: In Fedora 24 we can find the new dd from coreutils 8.25.5 which has a new fancier output format: Example #1: 1+0 records in 1+0 records out 4096 bytes (4.1 kB, 4.0 KiB) copied, 0.00887814 s, 461 kB/s ^^^^^^^^^^^^^^^^^ Example #2: 0+1 records in 0+1 records out 30 bytes copied, 0.00156704 s, 19.1 kB/s ^^^^ Compare with the old dd output found in Fedora 23: Example #1: 1+0 records in 1+0 records out 4096 bytes (4.1 kB) copied, 0.00135703 s, 3.0 MB/s ^^^^^^^^ Example #2: 0+1 records in 0+1 records out 30 bytes (30 B) copied, 0.0033204 s, 9.0 kB/s ^^^^^^ Version-Release number of selected component (if applicable): Vdsm: all versions coreutils: >= 8.25.5 How reproducible: 100% Steps to Reproduce: 1. Install Vdsm in any system which runs coreutils >= 8.25.5, like fedora 24 2. Run Vdsm 3. storage readspeed breaks Actual results: Vdsm can't estimate the read speed of the storage using dd Expected results: No issue Additional info: The format of dd is not meant for program consumption, so has not stable guarantee. Vdsm should just keep up.
This change will be included in 4.1's build. If you think this is worthy of backporting, please set back to POST and backport it.
Patch was backported to 4.0.z (which is probably the right call), resetting status and flags accordingly.
Since we don't check over Fedora, for verification, a regression test was done. Storage domain creation and domain monitor works as expected using RHEL7.2 hypervisor. rhevm-4.0.2-0.1.rc.el7ev.noarch vdsm-4.18.9-1.el7ev.x86_64