RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

virt-what 1.18 was released today:

https://www.redhat.com/archives/virt-tools-list/2017-July/msg00172.html

Currently RHEL 7.4 carries a downstream version of virt-what which
basically consists of all the upstream commits (before 2017/02)
without any version number changes:

http://git.annexia.org/?p=virt-what.git;a=shortlog;h=refs/heads/rhel-7.4

In other words: It's a rebase in all but name.

It may be better to actually rebase virt-what instead, and since
virt-what 1.18 will be in Fedora for 3 or 4 months before RHEL 7.5
comes out it should get plenty of testing.

virt-what has an upstream stable ABI policy so there should be
no regressions by doing this.

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

Current: virt-what-1.13-10.el7
Intended: virt-what 1.18

Some other bugs which would be fixed by the rebase:

https://bugzilla.redhat.com/show_bug.cgi?id=1472871
https://bugzilla.redhat.com/show_bug.cgi?id=1455676
https://bugzilla.redhat.com/show_bug.cgi?id=1467878

FWIW, just a note related to s390x:
To support KVM on s390x in virt-what, we need http://git.annexia.org/?p=virt-what.git;a=commitdiff;h=89c3d9e094934405266688d2061fe1105863ca17 ... so this should be fixed by the rebase to version 1.18, too. (In the unlikely case that the rebase does not happen, we should remember to backport that patch instead)

Rich, can you please provide text for release notes? Thanks.

Verified with the package:
virt-what-1.18-4.el7	

Automation test result: 
https://polarion.engineering.redhat.com/polarion/#/project/RedHatEnterpriseLinux7/testrun?id=libguestfs-1_36_10-6_el7%20RHEL-7_5-20180125_0%20x86_64%202018-01-27%2018-21-48
Manual test result:
https://polarion.engineering.redhat.com/polarion/#/project/RedHatEnterpriseLinux7/testrun?id=libguestfs-1_36_10-3_el7%20RHEL-7_5-20171130_0%20manual%20test%20run

Result: PASSED

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/RHBA-2018:0896