Bug 1481948

Summary: Include wrong kernel in redhat-virtualization-host-4.1-20170815.0
Product: Red Hat Enterprise Virtualization Manager Reporter: cshao <cshao>
Component: rhev-hypervisor-ngAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: cshao <cshao>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.5CC: apinnick, dfediuck, dguo, huzhao, jiawu, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.1.5Keywords: Rebase, ZStream
Target Release: ---Flags: rbarry: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: redhat-virtualization-host-4.1-20170816.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-22 17:44:45 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:

Description cshao 2017-08-16 06:43:51 UTC 
Description of problem:
Include wrong kernel in redhat-virtualization-host-4.1-20170815.0

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.1-20170815.0
imgbased-0.9.43-0.1.el7ev.noarch
kernel-3.10.0-693.2.1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install redhat-virtualization-host-4.1-20170815
2. Login RHVH, check kernel version.
3. # rpm -qa| grep kernel
kernel-tools-libs-3.10.0-693.2.1.el7.x86_64
kernel-tools-3.10.0-693.2.1.el7.x86_64
kernel-3.10.0-693.2.1.el7.x86_64


Actual results:
Include wrong kernel in redhat-virtualization-host-4.1-20170815.0

Expected results:
RHVH should include the shipped kernel package(kernel-3.10.0-693.1.1.el7).

Additional info:
Comment 2 cshao 2017-08-18 05:20:31 UTC 
Test version:
rhvh-4.1-0.20170817.0+1
kernel-3.10.0-693.1.1.el7.x86_64

Test result:
RHVH include the correct kernel package, so the bug is fixed, change bug status to VERIFIED.
Comment 5 errata-xmlrpc 2017-08-22 17:44:45 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/RHBA-2017:2529