Bug 1722173

Summary: missing iperf3 on RHV-H
Product: Red Hat Enterprise Virtualization Manager Reporter: Ricky Nelson <rnelson>
Component: ovirt-hostAssignee: Yuval Turgeman <yturgema>
Status: CLOSED ERRATA QA Contact: cshao <cshao>
Severity: high Docs Contact:
Priority: medium    
Version: 4.2.8-4CC: cshao, jcall, lsurette, lsvaty, mavital, mtessun, nlevy, qiyuan, rdlugyhe, sbonazzo, seamurph, weiwang, yaniwang, ycui, yturgema
Target Milestone: ovirt-4.3.5Keywords: ZStream
Target Release: 4.3.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-host-4.3.4-1.el7ev Doc Type: Bug Fix
Doc Text:
Previously, iperf3 RPMs were missing from the optional Red Hat Virtual Host (RHVH) repository, rhel-7-server-rhvh-4-rpms. The current release adds the iperf3 package to the RHVH image instead of the optional repository.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-12 11:55:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1728283    

Description Ricky Nelson 2019-06-19 15:19:36 UTC
Description of problem:
The rhel-7-server-rhvh-4-rpms repo should have the iperf3 RPMs and dependencies. During a case where we needed to document and troubleshoot the underlying performance of the network throughput, Support and Engineering requested that we install iperf3.

The RPMs were not located in the channel, so we are going to deliver the RPM and dependencies via tarball.


Version-Release number of selected component (if applicable):
The rhel-7-server-rhvh-4-rpms repo.


Actual results:
iperf3 and dependencies not within rhel-7-server-rhvh-4-rpms repo

Expected results:
iperf3 and dependencies within the rhel-7-server-rhvh-4-rpms repo

Comment 2 Ricky Nelson 2019-06-19 22:56:43 UTC
I have a RHHI-V 1.5 environment up and running, so I haven't tested this on the latest bits delivered with 1.6, but when I installed it looks like all the dependencies were already present. Here's a -qR:



[root@rhhi1 ~]# rpm -q iperf3
iperf3-3.1.7-2.el7.x86_64
[root@rhhi1 ~]# rpm -qR iperf3
libc.so.6()(64bit)
libc.so.6(GLIBC_2.11)(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.15)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.7)(64bit)
libiperf.so.0()(64bit)
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1

Comment 3 Wei Wang 2019-06-20 06:44:54 UTC
Test Version:
rhvh-4.2.11.1-0.20190618.0
imgbased-1.0.31-1.el7ev.noarch
subscription-manager-1.21.10-3.el7_6.x86_64


Test Steps:
1. Clean install RHVH 4.2.11
2. Subscribe to RHSM
3. Enable rhel-7-server-rhvh-4-rpms repo
4. Install iperf3

Result:
iperf3 and dependencies not within rhel-7-server-rhvh-4-rpms repo

[root@dell-perxxx-xx ~]# yum install iperf3
Loaded plugins: enabled_repos_upload, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade
No package iperf3 available.
Error: Nothing to do
Uploading Enabled Repositories Report
Loaded plugins: product-id, subscription-manager


QE can reproduce, ACK+

Comment 4 Yuval Turgeman 2019-06-20 06:58:48 UTC
Isn't this an RFE ?

Comment 7 Sandro Bonazzola 2019-07-08 14:39:54 UTC
Decided to include iperf3 within the image itself.

Comment 10 cshao 2019-07-11 06:56:23 UTC
Test version:
redhat-virtualization-host-4.3.5-20190710.2.el7_7
ovirt-host-4.3.4-1.el7ev

Test result:
# rpm -qa| grep iperf3
iperf3-3.1.7-2.el7.x86_64

So the bug is fixed, change bug status to VERIFIED.

Comment 13 errata-xmlrpc 2019-08-12 11:55:53 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, 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/RHEA-2019:2451