Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionDylan Stephano-Shachter
2020-05-19 22:10:04 UTC
Description of problem:
The version of osinfo-db that ships in rhel 8 is rather old. This makes it difficult to use rhel as a hypervisor in a production environment as it does not have the proper information to run, for example, fedora32 hosts.
Version-Release number of selected component (if applicable):
osinfo-db-20190611-1.el8.noarch
Additional info:
I would be willing to help maintain an up to date version of this package if someone points me in the direction of how to do that.
Dylan,
Due to RHEL processes it's almost impossible to keep the db up-to-date as we wish.
However, a non-supported way to work this around would be using osinfo-db-tools and importing the latest releases from upstream.
Mind, tho, this would be a non-supported way.
Comment 3Dylan Stephano-Shachter
2020-05-20 17:44:26 UTC
Fabiano,
That is rather unfortunate but I definitely believe it. I'm just curious, what would Red Hat say if you wanted to install Fedora 32 on a RHEL host? Is this just not supported?
(In reply to Dylan Stephano-Shachter from comment #3)
> Fabiano,
>
> That is rather unfortunate but I definitely believe it. I'm just curious,
> what would Red Hat say if you wanted to install Fedora 32 on a RHEL host? Is
> this just not supported?
What's actually blocking you to install Fedora 32 on RHEL host? This is the bit that I don't understand.
As I pointed out, there are ways admins can use newer osinfo-db, using it through osinfo-db-tools is one way.
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 (libosinfo bug fix and enhancement 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/RHBA-2020:4758