Bug 1375131

Summary: libosinfo should include the new version of rhel 7.3 and rhel 6.8
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libosinfoAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: cfergeau, juzhou, mclasen, mxie, mzhan, tlavigne, tpelka, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: libosinfo-0.3.0-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 04:43:58 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:

Description tingting zheng 2016-09-12 08:49:40 UTC
Description of problem:
libosinfo should include the new version of rhel 7.3 and rhel 6.8

Version-Release number of selected component (if applicable):
libosinfo-0.3.0-1.el7.x86_64
libvirt-2.0.0-8.el7.x86_64
virt-manager-1.4.0-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Launch virt-manager and Select "Network Install(HTTP,FTP or NFS)".
2. In Step2 of 5, input:http://download.eng.pek2.redhat.com/pub/rhel/rel-eng/RHEL-7.3-20160908.3/compose/Server/x86_64/os/,then check automatically detect version,it detects the version as rhel7.2.
3. Check "OS type" and "Version",there is no "rhel7.3 and rhel6.8".

Actual results:
As description.

Expected results:
libosinfo should include the new version of rhel6.8 and rhel7.3.

Additional info:

Comment 3 Tomas Pelka 2016-09-12 15:14:50 UTC
Tom would you please provide pm_ack and blocker flag.

Thank you
-Tom

Comment 8 errata-xmlrpc 2016-11-04 04:43:58 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://rhn.redhat.com/errata/RHBA-2016-2367.html