Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
Chapter 5. Updating Red Hat Hyperconverged Infrastructure
Updating involves moving from one version of a product to another minor release of the same product version, for example, from Red Hat Virtualization 4.1 to 4.1.3.
Red Hat recommends updating your systems regularly to apply security and bug fixes and take advantage of minor enhancements that are made available between major product releases.
5.1. Update workflow
Red Hat Hyperconverged Infrastructure is a software solution comprised of several different components. Apply updates in the following order to minimize disruption.
- Hosted Engine virtual machine
- Physical hosts
5.2. Before you update
Ensure that your Hosted Engine virtual machine is subscribed to the
rhel-7-server-rhvh-4-rpmsandrhel-7-server-rhv-4-tools-rpmsrepositories.# subscription-manager repos --enable=rhel-7-server-rhv-4.1-rpms # subscription-manager repos --enable=rhel-7-server-rhv-4-tools-rpms
Ensure that all physical machines are subscribed to the
rhel-7-server-rhvh-4-rpmsrepository.# subscription-manager repos --enable=rhel-7-server-rhv-4-rpms
If geo-replication is configured, ensure that data is not being synchronized.
- Check the Tasks subtab and ensure that there are no ongoing tasks related to Data Synchronization. If data synchronization tasks are present, wait until they are complete before beginning the update.
Stop all geo-replication sessions so that synchronization will not occur during the update. Click the Geo-replication subtab and select the session that you want to stop, then click Stop.
Alternatively, run the following command to stop a geo-replication session.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL stop
5.3. Updating the Hosted Engine virtual machine
Follow the steps in the following section of the Red Hat Virtualization Upgrade Guide to update the Hosted Engine virtual machine: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/chap-updates_between_minor_releases#Upgrading_between_Minor_Releases
5.4. Updating the physical hosts
Follow the steps in the sections linked below to update the physical hosts one at a time.
Between updates, ensure that you wait for any heal operations to complete before updating the next host. You can view heal status in the Bricks subtab. Alternatively, run the following command for every volume, and ensure that Number of entries: 0 is displayed for each brick before updating the next host.
# gluster volume heal VOLNAME info
Most updates can be applied using Red Hat Virtualization Manager. Follow the steps in the following section of the Red Hat Virtualization Upgrade Guide to update the physical host machines one at a time: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/updating_virtualization_hosts.
If you need to apply a security fix, apply updates manually instead. Follow the steps in the following section of the Red Hat Virtualization Upgrade Guide: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/Manually_Updating_Virtualization_Hosts
Remember to move your hosts out of maintenance mode when their updates have been applied by running the following command:
# hosted-engine --set-maintenance --mode=none
