Chapter 2. RHEA-2016:0375 ovirt-hosted-engine-setup

ovirt-hosted-engine-setup

BZ#1167074

Previously, iptables-services was not a required package during hosted-engine deployment, so hosted-engine was unable to configure iptables. Now, iptables-services is required, so hosted-engine can configure iptables correctly.

Copy to Clipboard Toggle word wrap

BZ#1216172

Previously, HostId was treated as an integer on the first host and as a string on additional hosts due to bad parsing of the answerfile, causing setup to fail. Now, this failure has been fixed by treating HostId as an integer on all hosts.

Copy to Clipboard Toggle word wrap

BZ#1251912

Previously, if more than one data center was defined in Red Hat Enterprise Virtualization Manager while using tagged VLANs, 'hosted-engine --deploy' failed updating the VLAN property on the management network. Now, multiple data centers are handled correctly.

Copy to Clipboard Toggle word wrap

BZ#1077850

With this release, you can deploy the Self-Hosted Engine with a virtual appliance image instead of an operating system ISO image.

Copy to Clipboard Toggle word wrap

BZ#1116469

Previously, after a power outage or another disruptive event, the hosted-engine.lockspace file refused to accept new connections, and virtual machines failed to start. The --reinitialize-lockspace command line option has been added to the hosted-engine command, which reinitializes the sanlock lockspace file and wipes all locks. This option is available only in clusters in global maintenance mode with all high availability agents shut down. Additionally, the --force option can be used with the --reinitialize-lockspace option to override the safety checks, but should be only used with caution.

Copy to Clipboard Toggle word wrap

BZ#1198138

With this release, users can attach a cloud-init ISO image to automatically configure the RHEVM Appliance from hosted-engine setup.

Copy to Clipboard Toggle word wrap

BZ#1196038

With this update, hosted-engine-setup is able to deploy the Red Hat Enterprise Virtualization Manager bridge using a bonded VLAN interface.

Copy to Clipboard Toggle word wrap

BZ#1191074

Previously, user defined iptables rules were overwritten when the host was added to the Manager and the automatic configuration of the firewall was turned off. Now, when the automatic configuration of the firewall is turned off the iptables rules will not be rewritten.

Copy to Clipboard Toggle word wrap

BZ#1169290

Previously, the self-hosted engine was talking with the VDSM-wrapping vdsClient utility. This could cause SSL timeout errors for long sync commands. With this release, the self-hosted engine uses the vdscli library for storage operations instead of vdsClient, reducing SSL timeouts.

Copy to Clipboard Toggle word wrap

BZ#1155637

Additional VDSM flags have been added to improve handling of pre-existing storage domains in hosted engine deployments.

Copy to Clipboard Toggle word wrap

BZ#1241426

Previously, a value for OVEHOSTED_CORE/nodeSetup was set later in the hosted-engine setup script, which caused an error if the user decided to abort setup at the first question, when the script tried to access OVEHOSTED_CORE/nodeSetup and found nothing. This was fixed by initially setting a default value for OVEHOSTED_CORE/nodeSetup, so the user can abort setup at the first question without errors.

Copy to Clipboard Toggle word wrap

BZ#1153278

With this update, users can now deploy self-hosted engine environments using fibre channel storage domains.

Copy to Clipboard Toggle word wrap

BZ#1139793

Previously, every host in a self-hosted engine environment stored a configuration file for the self-hosted engine virtual machine. As a result, any change to the configuration required users to update the file on each host. Now, a single self-hosted engine configuration file is saved on shared storage, and can be accessed by all hosts.

Copy to Clipboard Toggle word wrap

BZ#1131918

Previously, hosted-engine-setup was letting the user choose an invalid interface to create the management bridge on. Now, the list of allowed responses is better filtered.

Copy to Clipboard Toggle word wrap

BZ#1205663

With this release, users can override the RHEVM Appliance's default memory value during hosted-engine deployment.

Copy to Clipboard Toggle word wrap

BZ#1120780

Users can now add an answerfile entry to enable automatic shutdown of a virtual machine at the end of the hosted engine deployment process. This allows for full automation of the process.

Copy to Clipboard Toggle word wrap

BZ#1108341

Previously, when manually deploying a hosted engine, deployment would fail if the admin password provided in the hosted-engine setup on the host did not match the admin password provided in the engine-setup on the virtual machine. Now, the user will be prompted again until the passwords match.

Copy to Clipboard Toggle word wrap

BZ#1101297

With this release, Self-Hosted Engine setup can be fully automated by using the RHEV-M Virtual Appliance and dynamically configuring it with cloud-init.

Copy to Clipboard Toggle word wrap

BZ#1215437

Previously, hosted-engine-setup had the capability to redeploy a host reusing the same host ID it was using before, but this was not allowed for host 1. With this release, it is now possible to redeploy host 1 reusing the same host ID.

Copy to Clipboard Toggle word wrap

BZ#1083025

With this release, Gluster storage can be used as a data domain on the Self-Hosted Engine.

Copy to Clipboard Toggle word wrap

BZ#1234915

This release rebases package(s) to version 1.3.0.

Copy to Clipboard Toggle word wrap

BZ#1211532

With this release, hosted engine setup auto-detects available Appliance images and suggests them for use during installation.

Copy to Clipboard Toggle word wrap

BZ#1227366

Fully automated setup is now the default option in hosted engine setup, using cloud-init and the RHEV-M Appliance.
Setup also recommends to install the appliance if it is missing.

Copy to Clipboard Toggle word wrap

BZ#1217106

The self-hosted engine setup work flow has been improved. By using the RHEV-M Virtual Appliance instead of the traditional operating system installation for the Manager virtual machine, the setup time now takes less than 10 minutes (excluding the RPM download time).

Copy to Clipboard Toggle word wrap

BZ#1305885

This release rebases package(s) to version 1.3.3.3.

Copy to Clipboard Toggle word wrap

BZ#1177800

Previously, using multipath IO, each device was represented as physical devices (/dev/sdx) mapped together. Now, instead of showing each physical device, the LUN list provided during deployment shows the GUID of the multipath device.

Copy to Clipboard Toggle word wrap

BZ#1169792

Previously, hosted-engine-setup was checking for the ISO image to be readable by the VDSM user, but it was the KVM user that needed to read it to work properly. If the ISO image was readable by the VDSM user without being readable by the KVM user, the check passed but the virtual machine was still unable to boot from the ISO. With this release, hosted-engine-setup has a coherent permission check. Now if the ISO image passes the check, it works.

Copy to Clipboard Toggle word wrap

BZ#1254838

Previously, hosted-engine setup always used the Manager CA certificate to trust the signature of the REST API (apache) certificate, but some users replaced that with an externally signed one. In that case the validation, and so the deployment of additional hosts, failed. With this release, hosted-engine setup lets the user specify the local path of an external CA file, or proceed in insecure mode, if validation with the internal CA certificate fails.

Copy to Clipboard Toggle word wrap

BZ#1253939

Previously, VDSM used a heuristic to configure the default route property based on the bridge name. This was removed in Red Hat Enterprise Virtualization 3.6 as the name was not mandatory. However, this caused the default bridge property not to be configured for a hosted engine. Now, VDSM explicitly sets the default bridge property.

Copy to Clipboard Toggle word wrap

BZ#1254104

Previously, hosted engine deployment over iSCSI using the RHEVM-appliance failed with an endless loop if the destination storage had insufficient space. This has now been fixed.

Copy to Clipboard Toggle word wrap

BZ#1249118

Previously, ovirt-hosted-engine-setup assumed that if an answer file was passed to the command line on an additional host, it was generated by ovirt-hosted-engine-setup in a previous execution on the first host. When the host is RHEV-H an answer file is always passed to ovirt-hosted-engine-setup. On additional hosts based on RHEV-H, the ovirt-hosted-engine-setup failed. With this release, an additional question has been added to setup to confirm whether the answer file is the one generated on the first host. Now setup works on additional hosts.

Copy to Clipboard Toggle word wrap

BZ#1032069

Previously, the correctness of an ISO file type was not enforced at the customization level, so the user could pass an invalid file, causing the virtual machine to refuse to boot. This error has now been fixed.

Copy to Clipboard Toggle word wrap

BZ#1101553

The tool previously used vdsClient for interacting with VDSM. Now it uses vdscli API, resulting in better error handling and more control.

Copy to Clipboard Toggle word wrap

BZ#1210763

Previously, the length of a username wasn't checked, even though the database field was limited to store only 50 characters. A user could enter a username longer than 50 characters, causing an error while storing the username into the database during the setup. With this release, username length is now validated to ensure it can fit in the database. The user can no longer enter usernames which may cause the database insert to fail due to their length. Please note: work is in progress to modify the database to allow longer usernames, so in future this limitation will be lifted.

Copy to Clipboard Toggle word wrap

BZ#1215436

It is now possible to connect to the serial console of the engine virtual machine using a text-only connection when deploying the self-hosted engine. Instructions for connecting to the serial console are provided during the deployment process.

Copy to Clipboard Toggle word wrap