Bug 1689817

Summary: virt-manager cannot detect operating system name for rhel8.0.0 tree automatically
Product: Red Hat Enterprise Linux 8 Reporter: zhoujunqin <juzhou>
Component: osinfo-dbAssignee: Fabiano Fidêncio <fidencio>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: bgollahe, jkoten, knoel, mtessun, mxie, toneata, tzheng, xiaodwan, zili
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.1   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: osinfo-db-20190504-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:58:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description zhoujunqin 2019-03-18 08:31:27 UTC 
Description of problem:
virt-manager cannot detect operating system name for rhel8.0.0 tree automatically

Version-Release number of selected component (if applicable):
virt-manager-2.0.0-4.el8.noarch
libosinfo-1.2.0-5.el8.x86_64
osinfo-db-20181011-8.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install a new vm via virt-manager.
Launch virt-manager->click "Create a new virtual machine"-> Select "Network Install" method-> click "Forward" button-> Input URL "http://download.eng.pek2.redhat.com/pub/rhel/rel-eng/RHEL-8.0.0-20190313.0/compose/BaseOS/x86_64/os/"

Actual results:
virt-manager cannot detect rhel8.0.0 operating system you're installing from the installation media/source automatically.

Expected results:
Fix it.

Additional info:
1. check virt-manager debug info
...
[Mon, 18 Mar 2019 16:22:36 virt-manager 18261] DEBUG (urlfetcher:70) Fetching URI: http://download.eng.pek2.redhat.com/pub/rhel/rel-eng/RHEL-8.0.0-20190313.0/compose/BaseOS/x86_64/os/.treeinfo
[Mon, 18 Mar 2019 16:22:36 virt-manager 18261] DEBUG (urldetect:60) treeinfo family=Red Hat Enterprise Linux
[Mon, 18 Mar 2019 16:22:36 virt-manager 18261] DEBUG (urldetect:64) Found treeinfo version=8.0.0
[Mon, 18 Mar 2019 16:22:36 virt-manager 18261] DEBUG (urldetect:68) Found treeinfo name=Red Hat Enterprise Linux 8.0.0

2. 
Background: From snapshot 5, RCM has changed the name format of RHEL8 compose 
RHEL-8.0-20190108 --> RHEL-8.0.0-20190108
# wget http://download.eng.pek2.redhat.com/pub/rhel/rel-eng/RHEL-8.0.0-20190228.1/compose/BaseOS/x86_64/os/.treeinfo
# cat .treeinfo
arch = x86_64
family = Red Hat Enterprise Linux
name = Red Hat Enterprise Linux 8.0.0
packagedir = Packages
platforms = x86_64,xen
repository = .
timestamp = 1551390302
variant = BaseOS
variants = BaseOS
version = 8.0.0

3. Check file  /usr/share/osinfo/os/redhat.com/rhel-8.0.xml
# head  /usr/share/osinfo/os/redhat.com/rhel-8.0.xml
<libosinfo version="0.0.1">
<!-- Licensed under the GNU General Public License version 2 or later.
     See http://www.gnu.org/licenses/ for a copy of the license text -->
  <os id="http://redhat.com/rhel/8.0">
    <short-id>rhel8.0</short-id>
    <name>Red Hat Enterprise Linux 8.0</name>
    <version>8.0</version>
    <vendor>Red Hat, Inc</vendor>
    <vendor xml:lang="ca">Red Hat, Inc</vendor>
    <vendor xml:lang="de">Red Hat, Inc</vendor>

Summary: It uses old name format "Red Hat Enterprise Linux 8.0" and need to be updated, thanks.
Comment 1 Fabiano Fidêncio 2019-03-18 09:01:27 UTC 
(In reply to zhoujunqin from comment #0)
> Description of problem:
> virt-manager cannot detect operating system name for rhel8.0.0 tree
> automatically

This also affects ISO detections, not only trees.

> 
> Version-Release number of selected component (if applicable):
> virt-manager-2.0.0-4.el8.noarch
> libosinfo-1.2.0-5.el8.x86_64
> osinfo-db-20181011-8.el8.noarch

Yep, this is a consequence of not being able to update osinfo-db as regularly as we should. :-)
It's already too late (according to my understanding) for 8.0.0.

What we can do is have it merged for the next z-stream.
Comment 7 errata-xmlrpc 2019-11-05 20:58:09 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/RHSA-2019:3387