Bug 1400015 - Build RHEV-M Appliance for RHEV 4.0.6
Summary: Build RHEV-M Appliance for RHEV 4.0.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-appliance
Version: 4.0.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.6
: ---
Assignee: Yuval Turgeman
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 09:53 UTC by Fabian Deutsch
Modified: 2017-01-10 17:05 UTC (History)
4 users (show)

Fixed In Version: rhevm-appliance-20161130.0-1
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-10 17:05:30 UTC
oVirt Team: Node
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0055 0 normal SHIPPED_LIVE rhevm-appliance bug fix and enhancement update for RHV 4.0.6 2017-01-10 21:54:06 UTC

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


Note You need to log in before you can comment on or make changes to this bug.