Updated ovirt-hosted-engine-setup packages that fix several bugs and add variousenhancements are now available.

The ovirt-hosted-engine-setup package provides a self-hosted engine tool for RedHat Enterprise Virtualization Manager. A self-hosted engine is a virtualizedenvironment in which the Manager runs on a virtual machine on the hosts managedby the Manager. The self-hosted engine currently only runs on Red Hat EnterpriseLinux 6.5 hosts.A list of bugs fixed in this update is available in the Technical Notes book:

Before applying this update, make sure all previously released errata relevantto your system have been applied.This update is available via the Red Hat Network. Details on how to use the RedHat Network to apply this update are available at
Updated packages

Red Hat Enterprise Virtualization 3.4

    MD5: c2944b90d415802f62bb6736de8694b2SHA-256: 9afe5aee173a5750637df8ce3bed0c80937abc037545c367f1d51834bc6954cf
    MD5: 8360ece15071c3371da99e065012981eSHA-256: 632ee39d70936f8120a3c68798d66b885410a6c0bdff45caaef801d721164cec
(The unlinked packages above are only available from the Red Hat Network)Bugs fixed (see bugzilla for more information)

1024710 – engine vm should be powered off if user decides to reboot it and start again while hosted engine installation.1034634 – missing certificates generation cause virsh and spice connection to fail1034726 – When re-running –deploy, ha services should be stopped to allow re-using existing storage1044889 – [hosted engine] – TEXT – installation dialogue is misleading1044895 – [hosted engine] – TEXT – ‘screen’ in installation dialogue is not specific enough1044920 – PRD34 – [RFE][hosted engine] propose Default GW IP during installation1063576 – hosted-engine-setup not configuring libvirt correctly1069945 – [TEXT] Add a note explaining better how FQDN will be used1077150 – [Text] Poor description about storage free space requirements1079943 – engine vm can’t start1082028 – hosted-engine fails when cdrom is chosen as the source for the installation.1088572 – hosted-engine script fails with Traceback when cluster doesn’t return a CPU type

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

The Red Hat security contact is More contact details at

Leave a Reply