Este contenido no está disponible en el idioma seleccionado.
Chapter 2. Updates between Minor Releases
2.1. Updating the Red Hat Virtualization Manager Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Updates to the Red Hat Virtualization Manager are released via the Content Delivery Network. Before installing an update from the Content Delivery Network, ensure you read the advisory text associated with it and the latest version of the Red Hat Virtualization Manager Release Notes and Red Hat Virtualization Technical Notes on the Customer Portal.
Procedure 2.1. Updating Red Hat Virtualization Manager
- On the Red Hat Virtualization Manager machine, check if updated packages are available:
engine-upgrade-check
# engine-upgrade-checkCopy to Clipboard Copied! Toggle word wrap Toggle overflow - If there are no updates are available, the command will output the text
No upgrade:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note
If updates are expected, but not available, ensure that the required repositories are enabled. See Subscribing to the Required Entitlements in the Installation Guide. - If updates are available, the command will list the packages to be updated:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
- Update the ovirt-engine-setup package:
yum update ovirt-engine-setup
# yum update ovirt-engine-setupCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Update the Red Hat Virtualization Manager. By running
engine-setup, the script will prompt you with some configuration questions like updating the firewall rules, updating PKI certificates, and backing up the Data Warehouse database. The script will then go through the process of stopping theovirt-engineservice, downloading and installing the updated packages, backing up and updating the database, performing post-installation configuration, and starting theovirt-engineservice.Note
Theengine-setupscript is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values that were supplied. During an update, the stored values are displayed when previewing the configuration, and may not be up to date ifengine-configwas used to update configuration after installation. For example, ifengine-configwas used to updateSANWipeAfterDeletetotrueafter installation,engine-setupwill output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten byengine-setup.engine-setup
# engine-setupCopy to Clipboard Copied! Toggle word wrap Toggle overflow Important
The update process may take some time; allow time for the update process to complete and do not stop the process once initiated. - Update the base operating system and any optional packages installed on the Manager:
yum update
# yum updateCopy to Clipboard Copied! Toggle word wrap Toggle overflow Important
If any kernel packages were updated, reboot the system to complete the update.