Chapter 12. Updating IdM packages

Prerequisites

• Ensure you have applied all previously released errata relevant to the RHEL system. For more information, see the How do I apply package updates to my RHEL system? KCS article.

Procedure

• Select one of the following options:

  • Update the entire system (recommended). If your system has third-party repositories enabled, disable them first to avoid potential conflicts from external packages.

    For instructions on how to identify and disable repositories, see the Enabling or disabling a repository using Red Hat Subscription Management article.

    • After disabling any third-party repositories, update the system:

      # dnf update

      Copy to Clipboard Toggle word wrap

  • Alternatively, you can update only the IdM-related packages.

    Important

    This method only updates IdM packages. As a result, you might miss other important RHEL updates, including security patches and bug fixes.

    • To upgrade all IdM packages to the latest available version:

      # dnf upgrade ipa-* 389-ds-*

      Copy to Clipboard Toggle word wrap

    • To synchronize IdM packages to the latest version available from any enabled repository:

      # dnf distro-sync ipa-* 389-ds-*

      Copy to Clipboard Toggle word wrap

      After you update the IdM packages on at least one server, all other servers in the topology receive the updated schema, even if you do not update their packages. This ensures that any new entries which use the new schema can be replicated among the other servers.

  Warning

  When updating multiple IdM servers, wait at least 10 minutes after updating one server before updating another server. However, the actual time required for a server’s successful update depends on the topology deployed, the latency of the connections, and the number of changes generated by the update.

  When two or more servers are updated simultaneously or with only short intervals between the upgrades, there is not enough time to replicate the post-upgrade data changes throughout the topology, which can result in conflicting replication events.