Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1400015

Summary: Build RHEV-M Appliance for RHEV 4.0.6
Product: Red Hat Enterprise Virtualization Manager Reporter: Fabian Deutsch <fdeutsch>
Component: rhevm-applianceAssignee: Yuval Turgeman <yturgema>
Status: CLOSED ERRATA QA Contact: Gonza <grafuls>
Severity: high Docs Contact:
Priority: high    
Version: 4.0.5CC: dfediuck, gklein, rbarry, yturgema
Target Milestone: ovirt-4.0.6Keywords: Rebase, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhevm-appliance-20161130.0-1 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-10 17:05:30 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 Fabian Deutsch 2016-11-30 09:53:20 UTC
Build tracker

Comment 1 Sandro Bonazzola 2016-12-12 12:18:45 UTC
Can this be moved to QE?

Comment 2 Gonza 2016-12-14 12:10:09 UTC
Verified with:
rhevm-appliance-20161130.0-1.x86_64.rhevm.ova
Result:  PASS 

Smoke testing Passed 
* networking up. 
* init root passwords setup works. 
* disk resized to 50G 
* ovf indicates 4096 MB ram
* CPU: 2 (1:2:1 Sockets:Cores/S.:Threads/C.)
* rhevm setup works correctly. 
* rhevm admin portal is available after setup and login works. 
* Key Packages: 
heat-cfntools-1.2.6-5.el7.noarch
kernel-3.10.0-514.el7.x86_64
glibc-2.17-157.el7.x86_64
rhevm-4.0.6.2-0.1.el7ev.noarch
openssl-1.0.1e-60.el7.x86_64
ovirt-host-deploy-1.5.3-1.el7ev.noarch
rhevm-spice-client-x64-msi-4.0-3.el7ev.noarch
ovirt-engine-extension-aaa-jdbc-1.1.2-1.el7ev.noarch
rhevm-branding-rhev-4.0.0-6.el7ev.noarch
rhevm-setup-plugins-4.0.0.3-1.el7ev.noarch
rhevm-guest-agent-common-1.0.12-3.el7ev.noarch

Comment 4 errata-xmlrpc 2017-01-10 17:05:30 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/RHEA-2017:0055