Installation and Management Guide

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press u to select manage RHUI users.

3. From the User Manager screen, press p to select change admin’s password (followed by logout):

   -= User Manager =-
   
      p   change admin's password (followed by logout)
   
      rhui (users) => p
   
      Warning: After password change you will be logged out.
      Use ctrl-c to cancel password change.
      New Password:

4. Enter your new password; reenter it to confirm the change.

   New Password:
   Re-enter Password:
   
   [localhost] env PULP_SETTINGS=/etc/pulp/settings.py /usr/bin/pulpcore-manager reset-admin-password -p ********

Verification

1. The following message displays after you change the admin password:

   Password successfully updated. For security reasons you have been logged out.

Procedure

1. To upgrade to the latest version of RHUI, rerun the RHUI installer with the following command:

   $ podman run --pull=always -it --rm -v ~/.ssh/id_rsa:/ssh-keyfile:Z \
       registry.redhat.io/rhui5/installer-rhel9 rhui-installer \
       --target-user <target-user> --target-host <rhua-hostname> --rerun

2. Next, you will need to upgrade the CDS and HAProxy images by running the following command on RHUA:

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.
3. From the Repository Management screen, press a to select add a new Red Hat content repository.

4. Wait for the Red Hat Update Infrastructure Management Tool to determine the entitled repositories. This might take several minutes:

   rhui (repo) => a
   
   Loading latest entitled products from Red Hat...
   ... listings loaded
   Determining undeployed products...
   ... product list calculated

5. The Red Hat Update Infrastructure Management Tool prompts for a selection method:

   Import Repositories:
       1 - All in Certificate
       2 - By Product
       3 - By Repository
   Enter value (1-3) or 'b' to abort:

6. To add several repositories bundled together as a product—usually all the minor versions of it in one step—press 2 to select the By Product method. Alternatively, you can add particular repositories by using the By Repository method.

7. Select which repositories to add by typing the number of the repository at the prompt. You can also choose the range of repositories, for instance, by entering 1 - 5.

   Enter value (1-620) to toggle selection, 'c' to confirm selections, or '?' for more commands:

8. Continue until all repositories you want to add are checked.

9. Press c when you are finished selecting the repositories. The Red Hat Update Infrastructure Management Tool displays the repositories for deployment and prompts for confirmation:

   The following products will be deployed:
     Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI
     Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI
   Proceed? (y/n)

10. Press y to proceed. A message indicates each successful deployment:

    Importing Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10.1)...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10.0)...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10)...
    
    Importing Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI (10.1)...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI (10.0)...
      Importing product repository Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI (10)...
    
    Content will not be downloaded to the newly imported repositories
    until the next sync is run.

Verification

1. From the Repository Management screen, press l to check that the correct repositories have been installed.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.

3. From the Repository Management screen, press l to select list repositories currently managed by the RHUI:

   ...
   
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10)
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.0)
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.1)
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI (10)
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI (10.0)
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI (10.1)
   Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10)
   Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10.0)
   Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10.1)
   
   
   ...

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.

3. From the Repository Management screen, press i:

   Enter value (1-1631) to toggle selection, 'c' to confirm selections, or '?' for more commands:

4. Select the repository by entering the value beside the repository name. Enter one repository selection at a time before confirming your product selection.

5. Press c to confirm:

   Name:                Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Debug RPMs) from RHUI (10.1)
   ID:                  rhel-10-for-aarch64-appstream-debug-rhui-rpms-8.4
   Type:                Red Hat
   Version:             0
   Relative Path:       content/dist/rhel10/rhui/10.1/aarch64/appstream/debug
   GPG Check:           Yes
   Custom GPG Keys:     (None)
   Red Hat GPG Key:     Yes
   Content Unit Count:
   Last Sync:           2026-11-15 15:56:06
   Next Sync:           2026-11-15 22:00:00
   
   Name:                Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.1)
   ID:                  rhel-10-for-aarch64-appstream-rhui-rpms-8.4
   Type:                Red Hat
   Version:             0
   Relative Path:       content/dist/rhel10/rhui/10.1/aarch64/appstream/os
   GPG Check:           Yes
   Custom GPG Keys:     (None)
   Red Hat GPG Key:     Yes
   Content Unit Count:
   Last Sync:           2026-11-15 19:50:20
   Next Sync:           2026-11-16 01:55:00
   
   Name:                Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI (10.1)
   ID:                  rhel-10-for-aarch64-appstream-source-rhui-rpms-8.4
   Type:                Red Hat
   Version:             0
   Relative Path:       content/dist/rhel10/rhui/10.1/aarch64/appstream/source/SRPMS
   GPG Check:           Yes
   Custom GPG Keys:     (None)
   Red Hat GPG Key:     Yes
   Content Unit Count:
   Last Sync:           2026-11-15 15:56:51
   Next Sync:           2026-11-15 22:00:00

Verification

1. A similar output displays for your selections.

Tips and Tricks

1. Setting all repositories to on_demand right after installing RHUI can lead to faster deployment and quicker delivery for end-users, as only metadata needs to be initially synced.
2. Utilizing a cache priming strategy can be beneficial if you have a new installation and do not need to support older versions of RHEL clients. By using a client that mirrors end-user configurations and running dnf update, you can pre-download content to RHUI’s storage.

Procedure

1. On the RHUA node, create a YAML input file in the following format:

   # cat /root/example.yaml
   name: Example_YAML_File
   repo_ids:
       - rhel-10-for-x86_64-baseos-eus-rhui-rpms-10.0

2. Add the repositories listed in the input file using the rhui-manager utility:

   # rhua rhui-manager repo add_by_file --file /root/example.yaml --sync_now
   The name of the repos being added: Example_YAML_File
   Loading latest entitled products from Red Hat...
   ... listings loaded
   Successfully added Red Hat Enterprise Linux 10 for x86_64 - BaseOS - Extended Update Support from RHUI (RPMs) (10.0) (Yum)
   ... successfully scheduled for the next available timeslot.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.
3. From the Repository Management screen, press c to select create a new custom repository (RPM content only).

4. Enter a unique ID for the repository. Only alphanumeric characters, _ (underscore), and - (hyphen) are permitted. You cannot use spaces in the unique ID. For example, repo1, repo_1, and repo-1 are valid entries.

   Unique ID for the custom repository (alphanumerics, _, and - only):

5. Enter a display name for the repository. This name can contain spaces and other characters that could not be used in the ID. The name defaults to the ID.

   Display name for the custom repository [repo_1]:

6. Specify the path that will host the repository. The path must be unique across all repositories hosted by RHUI. For example, if you specify the path at this step as internal/rhel/9/repo_1, then the repository will be located at: https://<yourLB>/pulp/content/protected/internal/rhel/9/repo_1.

   Unique path at which the repository will be served [repo_1]:

7. Choose whether to protect the new repository. If you answer no to this question, any client can access the repository. If you answer yes, only clients with an appropriate entitlement certificate can access the repository.

   Warning

   As the name implies, the content in an unprotected repository is available to any system that requests it, without any need for a client entitlement certificate. Be careful when using an unprotected repository to distribute any content, particularly content such as updated client configuration RPMs, which will then provide access to protected repositories.

8. Answer yes or no to the following questions as they appear:

   Should the repository require clients to perform a GPG check and verify packages are signed by a GPG key? (y/n)
   
   Will the repository be used to host any Red Hat GPG signed content? (y/n)
   
   Will the repository be used to host any custom GPG signed content? (y/n)
   
   Enter the absolute path to the public key of the GPG key pair:
   
   Would you like to enter another public key? (y/n)
   
   Enter the absolute path to the public key of the GPG key pair:
   
   Would you like to enter another public key? (y/n)

9. The details of the new repository displays. Press y at the prompt to confirm the information and create the repository.

Verification

1. From the Repository Management screen, press l to check that the correct repositories have been installed.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.
3. From the Repository Management screen, press d at the prompt to delete a Red Hat repository. A list of all repositories currently being managed by RHUI displays.
4. Select which repositories to delete by typing the number of the repository at the prompt. Typing the number of a repository places a checkmark next to the name of that repository. You can also choose the range of repositories, for instance, by entering 1 - 5.
5. Continue until all repositories you want to delete are checked.

6. Press c at the prompt to confirm.

   Note

   After you delete a repository, the content of the repository (such as repodata and packages) will remain in the file system and can still be consumed by clients. Only after the next orphan cleanup task are the repository contents deleted, which means that clients may see 404 errors. In RHUI5 orphaned units are deleted weekly at 4am on Wednesday. An administrator can delete orphaned units at any time. You must update your client configuration RPM to avoid 404 errors.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.

3. From the Repository Management screen, press u:

   Select the repositories to upload the package into:
     -    1: test

4. Enter the value (1-1) to toggle the selection.
5. Press c to confirm your selection.

6. Enter the location of the packages to upload. If the location is an RPM, the file will be uploaded. If the location is a directory, all RPMs in that directory will be uploaded:

   /root/bear-4.1-1.noarch.rpm
   
   The following RPMs will be uploaded:
     bear-4.1-1.noarch.rpm

7. Press y to proceed or n to cancel:

   Copying RPMs to a temporary directory: /tmp/rhui.rpmupload.jsqdub22.tmp
   .. 1 RPMs copied.
   Creating repository metadata for 1 packages ...
   .. repository metadata created for 1 packages.
   The packages upload task for repo: client-config-rhel-10-x86_64 has been queued: /pulp/api/v3/tasks/01937826-8654-77c1-84f7-e9e07c7a7aeb/
   You can inspect its progress via (S)ync screen/(RR) menu option in rhui-manager TUI.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.

3. From the Repository Management screen, press ur:

   Select the repositories to upload the package into:
     -    1: test

4. Enter the value (1-1) to toggle the selection.

5. Press c to confirm your selection:

   ### WARNING ### WARNING ### WARNING ### WARNING ### WARNING ### WARNING ###
   #                                                                         #
   #   Content retrieved from non-Red Hat arbitrary places can contain       #
   #   unsupported or malicious software.  Proceed at your own risk.         #
   #                                                                         #
   ###########################################################################

6. Enter the remote URL of the packages to upload. If the location is an RPM, the file will be uploaded. If the location is a web page, all RPMs linked off that page will be uploaded:

   https://repos.fedorapeople.org/pulp/pulp/demo_repos/zoo/bear-4.1-1.noarch.rpm
   Retrieving https://repos.fedorapeople.org/pulp/pulp/demo_repos/zoo/bear-4.1-1.noarch.rpm
   
   The following RPMs will be uploaded:
     bear-4.1-1.noarch.rpm

7. Press y to proceed or n to cancel:

   Copying RPMs to a temporary directory: /tmp/rhui.rpmupload.dwux8rq7.tmp
   .. 1 RPMs copied.
   Creating repository metadata for 1 packages ...
   .. repository metadata created for 1 packages.
   The packages upload task for repo: test has been queued: /pulp/api/v3/tasks/0193770c-6523-7363-ae5e-8c6429728b4f/
   You can inspect its progress via (S)ync screen/(RR) menu option in rhui-manager TUI.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Enter r to select manage repositories.

3. On the Repository Management screen, enter r to select packages to remove from a repository (Custom RPM content only):

   -= Repository Management =-
   
      l   list repositories currently managed by RHUI
      i   display detailed information on a repository
      a   add a new Red Hat content repository
      ac  add a new Red Hat container
      c   create a new custom repository (RPM content only)
      d   delete a repository from RHUI
      u   upload content to a custom repository (RPM content only)
      ur  upload content from a remote web site (RPM content only)
      p   list packages in a repository (RPM content only)
      r   select packages to remove from a repository (Custom RPM content only)

4. Enter the value to select the repository:

   Choose a repository to delete packages from:
       1 - Test-RPM-1
       2 - Test-RPM-2

5. Enter the value to select the packages to delete.

   Select the packages to remove:
     -    1: example-package-1.noarch.rpm
     -    2: example-package-2.noarch.rpm

6. Enter c to confirm selection.

   The following packages will be removed:
     example-package-1.noarch.rpm

7. Enter y to proceed or n to cancel:

   Removed example-package-1.noarch.rpm

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press r to select manage repositories.
3. From the Repository Management screen, press p.

4. Select the number of the repository you want to view. The Red Hat Update Infrastructure Management Tool asks if you want to filter the results. Leave the line blank to see the results without a filter.

   Enter value (1-1631) or 'b' to abort: 1
   
   Enter the first few characters (case insensitive) of an RPM to filter the results
   (blank line for no filter):
   
   Only filtered results that contain less than 100 packages will have their
   contents displayed. Results with more than 100 packages will display
   a package count only.
   
   Packages:
     bear-4.1-1.noarch.rpm

Verification

1. One of three types of messages displays:

   Packages:
     bear-4.1-1.noarch.rpm

   Package Count: 8001

   No packages in the repository.

Procedure

1. On the RHUA node, run the following command.

   # rhua rhui-manager --noninteractive status --repo_json <output_file>*

   A JSON file is generated containing a list of dictionaries for all custom and Red Hat repositories. To view the content of the file, run the following command.

   # rhua cat <output_file>

2. If you would like to view the JSON file on the host, you can create the file in /root using the following command:

   # rhua rhui-manager --noninteractive status --repo_json /root/<output_file>

   Now you will be able to access your output file on the host machine as /var/lib/rhui/root/<output_file>

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press e to select create entitlement certificates and client configuration RPMs.
3. Press e to select generate an entitlement certificate.

4. Select which repositories to include in the entitlement certificate by typing the number of the repository at the prompt. Typing the number of a repository places an x next to the name of that repository. Continue until all repositories you want to add have been checked.

   Important

   Include only repositories for a single RHEL version in a single entitlement. Adding repositories for multiple RHEL versions leads to an unusable dnf configuration file.

5. Press c at the prompt to confirm.

6. Enter a name for the certificate. This name helps identify the certificate within the Red Hat Update Infrastructure Management Tool and generate the name of the certificate and key files.

   Name of the certificate. This will be used as the name of the certificate file
   (name.crt) and its associated private key (name.key). Choose something that will
   help identify the products contained with it.

7. Enter a path to save the certificate. Leave the field blank to save it to the current working directory.

8. Enter the number of days the certificate should be valid for. Leave the field blank for 365 days. The details of the repositories to be included in the certificate display.

   Repositories to be included in the entitlement certificate:
   
     Red Hat Repositories
       Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Debug RPMs) from RHUI
       Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI
       Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI
   
       Proceed? (y/n)

9. Press y at the prompt to confirm the information and create the entitlement certificate.

Verification

1. You will see a similar message if the entitlement certificate was created:

   ..........................+++++
   ....+++++
   Entitlement certificate created at ./rhel10-for-rhui5.crt
   
   ------------------------------------------------------------------------------

Procedure

1. Use the following command to create an entitlement certificate from the RHUI CLI:

   # rhua rhui-manager client cert --repo_label rhel-10-for-x86_64-appstream-eus-rhui-source-rpms --name rhuiclientexample --days 365 --dir /root/clientcert
   .............................................+++++
   ...............................................................................+++++
   Entitlement certificate created at /root/clientcert/rhuiclientexample.crt

   Note

   Use Red Hat repository labels, not IDs. To get a list of all labels, run the rhui-manager client labels command. If you include a protected custom repository in the certificate, use the repository’s ID instead.

Verification

1. A similar message displays if you successfully created and entitlement certificate:

   Entitlement certificate created at /root/clientcert/rhuiclientexample.crt

Procedure

1. Use the following command to create an RPM with the RHUI CLI:

   # rhua rhui-manager client rpm --entitlement_cert /root/clientcert/rhuiclientexample.crt --private_key /root/clientcert/rhuiclientexample.key --rpm_name clientrpmtest --dir /root --unprotected_repos unprotected_repo1
   Successfully created client configuration RPM.
   Location: /root/clientrpmtest-2.0/build/RPMS/noarch/clientrpmtest-2.0-1.noarch.rpm

   Note

   When using the CLI, you can also specify the URL of the proxy server to use with RHUI repositories, or you can use _none_ (including the underscores) to override any global dnf settings on a client machine. To specify a proxy, use the --proxy parameter.

Verification

1. A similar message displays if you successfully created a client configuration RPM:

   Successfully created client configuration RPM.
   Location: /root/clientrpmtest-2.0/build/RPMS/noarch/clientrpmtest-2.0-1.noarch.rpm

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press e to select create entitlement certificates and client configuration RPMs.
3. From the Client Entitlement Management screen, press c to select create a client configuration RPM from an entitlement certificate.

4. Enter the full path of a local directory to save the configuration files to:

   Full path to local directory in which the client configuration files generated by this tool
   should be stored (if this directory does not exist, it will be created):

5. Enter the name of the RPM.
6. Enter the version of the configuration RPM. The default version is 2.0.
7. Enter the release of the configuration RPM. The default release is 1.
8. Enter the full path to the entitlement certificate authorizing the client to access specific repositories.
9. Enter the full path to the private key for the entitlement certificate.
10. Select any unprotected custom repositories to be included in the client configuration.
11. Press c to confirm selections or ? for more commands.

Verification

1. A similar message displays if the RPM was successfully created:

   Successfully created client configuration RPM.
   Location: /root/clientrpmtest-2.0/build/RPMS/noarch/clientrpmtest-2.0-1.noarch.rpm

Procedure

1. In the following example, you will create a custom repository for the client configuration RPM for base RHEL 10 on the x86_64 architecture:

   # rhua rhui-manager repo create_custom --protected --repo_id client-config-rhel-10-x86_64 --display_name "RHUI Client Configuration for RHEL 9 on x86_64" --gpg_public_keys /root/RPM-GPG-KEY-my-cloud

   You can use a different repository ID and display name if desired, and ensure you specify the actual GPG key file.

2. Add the relevant Red Hat repositories. The following YAML file contains the typical set of repositories for base RHEL 10 on the x86_64 architecture, using unversioned repositories:

   # cat rhel-10-x86_64.yaml
   name: Red Hat Enterprise Linux 10 on x86_64
   repo_ids:
     - codeready-builder-for-rhel-10-x86_64-rhui-debug-rpms-8
     - codeready-builder-for-rhel-10-x86_64-rhui-rpms-8
     - codeready-builder-for-rhel-10-x86_64-rhui-source-rpms-8
     - rhel-10-for-x86_64-appstream-rhui-debug-rpms-8
     - rhel-10-for-x86_64-appstream-rhui-rpms-8
     - rhel-10-for-x86_64-appstream-rhui-source-rpms-8
     - rhel-10-for-x86_64-baseos-rhui-debug-rpms-8
     - rhel-10-for-x86_64-baseos-rhui-rpms-8
     - rhel-10-for-x86_64-baseos-rhui-source-rpms-8
     - rhel-10-for-x86_64-supplementary-rhui-debug-rpms-8
     - rhel-10-for-x86_64-supplementary-rhui-rpms-8
     - rhel-10-for-x86_64-supplementary-rhui-source-rpms-8

   To add and synchronize all these repositories using the YAML file above, run the following command:

   # rhua rhui-manager repo add_by_file --file rhel-10-x86_64.yaml --sync_now

3. Create an entitlement certificate. You will need a list of repository labels that are to be allowed in the certificate. Repository labels are often identical to repository IDs, except when the repository ID contains a specific RHEL minor version, in which case the label does not contain the minor version but only the major version. In the case of base RHEL repositories, the IDs are identical, so you can extract them from the YAML file above, using the following Python code:

   import yaml
   with open("rhel-10-x86_64.yaml") as repoyaml:
       repodata = yaml.safe_load(repoyaml)
       print(",".join(repodata["repo_ids"]))

   Copy the output to the clipboard and store it as an environment variable; for example, $labels:

   # labels=<paste the contents of the clipboard here>

   In addition to the RHEL repository labels, you also need to add the custom repository to the comma-separated list of labels when creating the entitlement certificate. Run the following command to create the entitlement certificate allowing access to both the RHEL repositories and the custom repository:

   # rhua rhui-manager client cert --name rhel-10-x86_64 --dir /root --days 3650 --repo_label $labels,client-config-rhel-10-x86_64

   If your company’s policy allows certificates to be valid for only one year, two years, etc., change the value of the --days argument accordingly.

   This command creates the files /root/rhel-10-x86_64.crt and /root/rhel-10-x86_64.key. You will need them in the next step.

4. Create a client configuration RPM:

   # rhua rhui-manager client rpm --dir /tmp --rpm_name rhui-client-rhel-10-x86_64 --rpm_version 1.0 --entitlement_cert /root/rhel-10-x86_64.crt --private_key /root/rhel-10-x86_64.key

   Use an RPM name or version of your choice. With the values above, the command creates the RPM and prints its location, which is:

    `/tmp/rhui-client-rhel-10-x86_64-1.0/build/RPMS/noarch/rhui-client-rhel-10-x86_64-1.0-1.noarch.rpm`
   . Transfer this RPM from the RHUA to your system and sign it with the appropriate GPG key—the
   private key that corresponds to the public key that you used as the `--gpg_public_keys` parameter
   when you created the custom repository. You can then, for example, have the signed RPM
   preinstalled on RHEL 8 x86_64 images in your cloud environment. You also need to transfer the
   signed RPM back to the RHUA and upload it to the custom repository for RHEL 8 on x86_64:

   # rhua rhui-manager packages upload --repo_id client-config-rhel-10-x86_64 --packages /root/signed/rhui-client-rhel-10-x86_64-1.0-1.noarch.rpm

Verification

1. Check the contents of the custom repository:

   # rhua rhui-manager packages list --repo_id client-config-rhel-10-x86_64

   This command is supposed to print the RPM file that you have uploaded.

2. Once you have configured your CDS and HAProxy nodes, which is described later in this guide, you can also install the client configuration RPM on a test VM and verify access to all the relevant repositories by running the following command on the test VM:

   # dnf -v repolist

   This command is supposed to print the configured RHEL 8 repositories and the custom repository for client configuration RPMs.

1. If you used 1.0 in the previous invocation, use e.g. 2.0 now, and keep the rest of the parameters:

   # rhua rhui-manager client rpm --dir /tmp --rpm_name rhui-client-rhel-10-x86_64 --rpm_version 2.0 ...

2. Then, again, sign the newer RPM, transfer it to the RHUA, and upload it to the custom repository:

   # rhua rhui-manager packages upload --repo_id client-config-rhel-10-x86_64 --packages /root/signed/rhui-client-rhel-10-x86_64-2.0-1.noarch.rpm

3. Client VMs on which the previous version of the RPM is installed will now be able to update to the newer version. Note that it may be necessary to clean the dnf cache on the client VM to make dnf reload the repodata, which was updated when the newer RPM was uploaded.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press n to select manage Red Hat entitlement certificates.

3. From the Entitlements Manager screen, press l to list data about the current content certificate:

   rhui (entitlements) => l
   
   Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Debug RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem
   
      Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem
   
      Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem
   
      Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem
   
      Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem
   
      Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Source RPMs) from RHUI
      Expiration: 02-27-2027     Certificate: c885597492374720bb5d398c3f65d1ed.pem

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press c to select manage content delivery servers (CDS).
3. From the Content Delivery Server (CDS) Management screen, press a to add a new CDS instance.

4. Enter the hostname of the CDS to add:

   Hostname of the CDS instance to register:
   cds1.example.com

5. Enter the user name that will have SSH access to the CDS and have sudo privileges.

   Username with SSH access to <cds1.example.com> and sudo privileges:
   <cloud-user>

6. Enter the absolute path to the SSH private key for logging in to the CDS and press Enter.

   Absolute path to an SSH private key to log into <cds1.example.com> as <cloud-user>:
   /home/<cloud-user>/.ssh/id_rsa_rhua

7. Update the instance with the latest versions of available packages

   Update instance after registering? (y/n): y

8. Optional: If you wish to use custom SSL certificates, enter the absolute path to the custom SSL certificate, SSL Key, and SSL crt files.

   Note

   If you do not provide an SSL certificate, it will be automatically generated.

   Optional absolute path to user supplied SSL key file:
   /home/<cloud-user>/custom_ssl.key
   
   Optional absolute path to user supplied SSL crt file:
   /home/<cloud-user>/custom_ssl.crt
   
   .........................................................................
   The following CDS has been successfully added:
   
     Hostname:             <cds1.example.com>
     SSH Username:         <cloud-user>
     SSH Private Key:      /home/<cloud-user>/.ssh/id_rsa_rhua
   
   The CDS will now be configured:
   ....................................................................
   The CDS was successfully configured.

9. If adding the content delivery server fails, check that the firewall rules permit access between the RHUA and the CDS.

10. Run the mount command to see if shared storage is mounted as read-write.

    [root@rhua ~]# mount | grep rhui
    
    nfs.example.com:/export on /var/lib/rhui/remote_share type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.8.41.163,local_lock=none,addr=10.8.41.163)

11. After successful configuration, repeat these steps for all remaining CDS nodes.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press c to select manage content delivery servers (CDS):

3. From the Content Delivery Server (CDS) Management screen, press l to list all known CDS nodes that RHUI 5} manages:

   Hostname:             <cds1.example.com>
   SSH Username:     <cloud-user>
   SSH Private Key:     /<cloud-user>/.ssh/id_rsa_rhua

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press c to select manage content delivery servers (CDS).
3. From the Content Delivery Server (CDS) Management screen, press r to select reinstall and reapply configuration to an existing CDS instance. The Red Hat Update Infrastructure Management Tool automatically performs all reinstallation and reconfiguration tasks.

4. Select the CDS to reinstall:

       1 -
       Hostname:             <cds1.example.com>
       SSH Username:     <cloud-user>
       SSH Private Key:     /<cloud-user>/.ssh/id_rsa_rhua

5. Enter a value or b to abort: 1: 1

6. Update instance(s) after reinstalling? (y/n): y

   Checking that the RHUA services are reachable from the instance...
   Done.
   
   
   Installing and configuring the CDS...
   
   PLAY [Registering a CDS instance] **********************************************
   
   ...
   
   TASK [Update CDS instance] *****************************************************
   ok: [cds1.example.com]
   
   PLAY RECAP *********************************************************************
   cloud-user@cds1.example.com : ok=24   changed=10   unreachable=0    failed=0    skipped=2    rescued=0    ignored=0
   
   Done.

Procedure

1. Transfer your legacy CA certificate to your CDS nodes and save it in the /etc/pki/rhui/legacy-ca/ directory.

2. Get the subject hash value from the certificate and keep it in a shell variable:

   #hash=`openssl x509 -hash -noout -in /etc/pki/rhui/legacy-ca/YOUR_CERT.crt`

3. Create a symbolic link to the certificate file in the /etc/pki/tls/certs/ directory with the hash and an unused number, starting from 0, as the symbolic link name:

   #ln -s /etc/pki/rhui/legacy-ca/YOUR_CERT.crt /etc/pki/tls/certs/$hash.0

   This action takes effect immediately.

Procedure

1. On the CDS node, navigate to the /etc/pki/rhui/legacy/ directory:

   # cd /etc/pki/rhui/legacy/

2. Optional: Back up the existing CA certificates:

3. Delete the CA certificate that corresponds to the CA you want to limit:

   # rm example-legacy.crt

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press c to select manage content delivery servers (CDS).
3. From the Content Delivery Server (CDS) Management screen, press d to delete a CDS instance.

4. Enter the hostname of the CDS to delete:

   Hostname of the CDS instance to unregister:
   cds1.example.com

Prerequisites

1. Make sure sshd is running on the HAProxy load-balancer node and that port 443 is open.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press l to select manage HAProxy load-balancer instances.
3. From the Load-balancer (HAProxy) Management screen, press a to add a new load-balancer instance.

4. Enter the hostname of the new load-balancer:

   Hostname of the HAProxy Load-balancer instance to register:
   <haproxy1.example.com>

5. Enter the username that will have SSH access to the load-balancer and have sudo privileges:

   Username with SSH access to cds.example.com and sudo privileges:
   <cloud-user>

6. Enter the absolute path to the SSH private key for logging in to the load-balancer instance and press Enter:

   Absolute path to an SSH private key to log into cds.example.com as <cloud-user>:
   /<cloud-user>/.ssh/id_rsa_rhua

7. Update the instance with the latest versions of available packages

   Update instance after registering? (y/n): y

8. Optional: Enter an optional absolute path to a user supplied HAProxy configuration file and press Enter.

   If you do not specify the path to a custom configuration file, the default file, /usr/share/rhui-tools/templates/haproxy.cfg, is used instead.

   Optional absolute path to user supplied HAProxy config file:
   
   .........................................................................
   The following load-balancer has been successfully added:
   
   Hostname:         <haproxy1.example.com>
   SSH Username:     <cloud-user>
   SSH Private Key:  /<cloud-user>/.ssh/id_rsa_rhua
   
   The load-balancer will now be configured:

9. If the load-balancer fails to add, check that the firewall rules permit access between the RHUA and the load-balancer.
10. After successful configuration, repeat these steps for any remaining load-balancer instances.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press l to select manage HAProxy load-balancer instances.

3. From the Load-balancer (HAProxy) Management screen, press l to list the load-balancer instances that RHUI manages:

   Hostname:             <haproxy1.example.com>
   SSH Username:     <cloud-user>
   SSH Private Key:     /<cloud-user>/.ssh/id_rsa_rhua

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press l to select manage HAProxy load-balancer instances.

3. From the Load-balancer (HAProxy) Management screen, press r to reinstall and reapply the configuration to a load-balancer instance.

   The Red Hat Update Infrastructure Management Tool automatically performs all reinstallation and reconfiguration tasks.

4. Select the load-balancer to reinstall:

       1 -
       Hostname:             <haproxy1.example.com>
       SSH Username:     <cloud-user>
       SSH Private Key:     /<cloud-user>/.ssh/id_rsa_rhua

5. Enter a value or b to abort: 1: 1

6. Update instance(s) after reinstalling? (y/n): y

   Installing and configuring the HAProxy Load-balancer...
   
   PLAY [Registering a load balancer instance] ************************************
   
   ...
   
   TASK [Update load balancer instance] *******************************************
   ok: [haproxy1.example.com]
   
   PLAY RECAP *********************************************************************
   cloud-user@haproxy1.example.com : ok=8    changed=3    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
   
   Done.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press l to select manage HAProxy load-balancer instances.
3. From the Load-balancer (HAProxy) Management screen, press d to delete a load-balancer instance.

4. Enter the hostname of the load-balancer to delete:

   Hostname of the load-balancer instance to unregister:
   <haproxy1.example.com>

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.

3. From the Synchronization Status screen, press dr:

   -= Repository Summary Synchronization Status =-
   
   Last Refreshed: 02:01:22
   (updated every 5 seconds, ctrl+c to exit)
   
   Last Sync                    Last Result
   -------------------------------------------------
   Red Hat Enterprise Linux 10 for ARM 64 - BaseOS (Debug RPMs) from RHUI (10)
     Never                        None
   ....
   ....
   Red Hat Enterprise Linux 10 for x86_64 - AppStream from RHUI (Debug RPMs) (10.1)
     2026-07-29 17:45:41          Running
   Associating Content: 11001 (97%)
   Downloading Artifacts: 7376

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.

3. From the Synchronization Status screen, press rr:

   Last Refreshed: 02:06:46
   (updated every 5 seconds, ctrl+c to exit)
   
   Current Sync                 Result
   -------------------------------------------------
   Red Hat Enterprise Linux 10 for x86_64 - AppStream from RHUI (Debug RPMs) (10.0)
     2026-07-29 17:45:41          Running
   Associating Content: 11001 (97%)
   Downloading Artifacts: 7376

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.
3. From the Synchronization Status screen, press vr.

4. Enter the number for the repository that you want to see details for:

   Enter value (1-66) or 'b' to abort:

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.

3. From the Synchronization Status screen, press sr:

   Select one or more repositories to schedule to be synchronized before its scheduled time.
   The sync will happen as soon as possible depending on other tasks that may be executing
   in the RHUI.  Sync requests for repositories with tasks in running
   or pending state will be ignored.
   
            Last Result  Next Sync              Repository
            -------------------------------------------------

4. Select the repository by entering the value beside the repository name. Enter one repository selection at a time before confirming your product selection:

   x  714: Error        2026-11-17 20:30:00    Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.0)

5. Press c to confirm:

   The following repositories will be scheduled for synchronization:
     Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.0)
   Proceed? (y/n) y

6. Press y to proceed:

   Scheduling sync for Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.0)...
   ... successfully scheduled for the next available timeslot.

   Note

   This message displays if a task for the selected repository is running. Ignoring sync request for Red Hat Enterprise Linux 10 for x86_64 - AppStream from RHUI (Debug RPMs) (10.0) as the repo is currently reserved by a running task.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.
3. From the Synchronization Status screen, press ca to select cancel active sync tasks.

4. Enter the value for the task or tasks that you want to cancel:

   Select one or more repositories for which you want to cancel their active tasks.
     -    1: Red Hat Enterprise Linux 10 for x86_64 - AppStream from RHUI (Debug RPMs) (10.0)
   Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for more commands:

5. Press c to confirm your selection.

6. Press y to cancel the synchronization task or tasks:

   The active tasks will be canceled for the following repositories:
     Red Hat Enterprise Linux 8 for x86_64 - AppStream from RHUI (Debug RPMs) (10.0)
   Proceed? (y/n)

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.

3. From the Synchronization Status screen, press ap:

   rhui (sync) => ap
   
   Select one or more repositories to toggle the auto-publish status.
   The operation will be executed as soon as possible depending on other tasks
   that may be executing in the RHUI.
   
                   Status | Repository
              --------------------------------------------------------------------------
   Select one or more repositories:
   
     Custom Repositories
   
     Red Hat Repositories: dnf
   
        -  713:       AUTO Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10)
        -  714:       AUTO Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.1)

4. Enter a value ( 1- 1631) to toggle the selection, c to confirm selections, or ? for more commands:

   The following repositories will have their auto-publish status changed:
     Red Hat Repositories
       dnf
          Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10.0)

5. Press c to confirm your selection.
6. Press y to proceed.

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.
3. From the Synchronization Status screen, press wf.

4. Enter a value ( 1- 1631) to toggle the selection, c to confirm selections, or ? for more commands:

   The following repositories will be scheduled for workflow push:
     Red Hat Repositories
       dnf
          Red Hat Enterprise Linux 10 for ARM 64 - AppStream (RPMs) from RHUI (10)

5. Press y to proceed:

Procedure

1. Navigate to the Red Hat Update Infrastructure Management Tool home screen:

   [root@rhua ~]# rhua rhui-manager

2. Press s to select synchronization status and scheduling.
3. From the Synchronization Status screen, press ex.
4. Enter a value to toggle the selection.

5. Press c to confirm the selection:

   The following repositories will be exported:
     Red Hat Repositories
       dnf
          Red Hat Enterprise Linux 10 for ARM 64 - AppStream (Source RPMs) from RHUI (10)

6. Press y to proceed.

Procedure

1. Stop RHUA services:

   # systemctl stop rhui_rhua

2. Verify whether the services have stopped:

   # systemctl status rhui_rhua

3. Back up the following files.

   # rsync -av --exclude .local --exclude remote_share /var/lib/rhui/ /BACKUP/DIRECTORY/

   Important

   Ensure that the files retain their current attributes when you back them up.

4. Back up any generated client entitlement certificates and client configuration RPMs.

   • Optional: If you want to back up the remote share from the RHUA without using a different backup solution for the file server, use the following command:

     # rsync -av /var/lib/rhui/remote_share/ /ANOTHER/BACKUP/DIRECTORY/

5. Restart RHUI services.

   # systemctl start rhui_rhua

Procedure

1. Stop the nginx service:

   # systemctl stop nginx

2. Verify that the nginx service has stopped:

   # systemctl status nginx

3. Back up the following files.

   # cp -a <source_files_path> <destination_files_path>

   Important

   Ensure that the files retain their current attributes when you back them up.

   List of files:

   • /etc/nginx/*
   • /var/log/nginx/*
   • /etc/pki/rhui/*

4. Restart RHUI services.

   # rhui-services-restart

Procedure

1. To configure (or unconfigure) proxy server settings, you will be creating (or editing) the local overrides file, /etc/rhui/rhui-tools.conf, so that it contains:

   [proxy]
   proxy_protocol: <PROTOCOL>
   proxy_host: <HOSTNAME>
   proxy_port: <PORT>
   proxy_user: <USERNAME>
   proxy_pass: <PASSWORD>

   Then, the parameters are as follows:

   • PROTOCOL is either http or https if configuring the proxy server; if unconfiguring it, when using the local file, leave the value empty
   • HOSTNAME is the new proxy server hostname; if clearing the configuration when using the local file, leave the value empty
   • PORT is the TCP port where the proxy server is listening, typically 3128; if clearing the configuration when using the local file, leave the value empty
   • USERNAME is an optional parameter. Only use it if the proxy server requires credentials. If it does not or you are clearing the configuration when using the local file, leave the value empty or do not use the proxy_user: option at all
   • PASSWORD is an optional parameter. Only use it if the proxy server requires credentials. If it does not or you are clearing the configuration when using the local file, leave the value empty or do not use the proxy_user: option at all

   • All commands must be run in the RHUA container

     Important

     This new configuration will only affect Red Hat repositories added after the configuration is updated. To apply this new configuration to existing repositories, it is necessary to remove, add, and re-synchronize the repositories.

     This will cause an outage that will last from the moment you remove them until you re-sync them. However, already synchronized packages will not have to be re-downloaded from the Red Hat CDN. RHUI will mainly have to parse all the repodata files and determine which package belongs where. This can take up to several hours.

     Although there are technical means outside of rhui-manager whereby the proxy fields can be modified for the existing repositories—or rather, for the so-called remotes—using such means is unsupported.

2. Make sure you have a list (or lists) of your repositories so that you can add them again. If you do not have such a list, you can use rhui-manager to generate a file with all your currently added Red Hat repositories.

3. To generate a list of Red Hat repositories, first create a raw list with one ID per line:

   rhui-manager --noninteractive repo list --redhat_only --ids_only > /root/rawlist

4. Then create a YAML file with repositories. Start by creating a stub:

   echo -e "name: all Red Hat repositories\nrepo_ids:" > /root/repo_list.yml

5. Next, append the repositories from the raw list as YAML list items:

   sed "s/^/  - /" /root/rawlist >> /root/repo_list.yml

6. Delete all Red Hat repositories from your RHUI:

   Use the text user interface, or delete them one by one on the command line. For the latter, you can use the raw list created earlier:

   while read repo; do rhui-manager --noninteractive repo delete --repo_id $repo; done < /root/rawlist

   Note

   Repositories are deleted in asynchronous background tasks: queued and executed by available Pulp workers. It may take tens of minutes, or hours, to actually delete all the repositories. Be patient.

7. When the repositories have been deleted, re-add them. They will be added with the new proxy settings (or with no proxy URL) this time. It is also necessary to re-synchronize the repositories. You can add and re-synchronize them in one step on the command line:

   rhui-manager --noninteractive repo add_by_file --file /root/repo_list.yml --sync_now

   Alternatively, use your own methods to synchronize the repositories, for example, in a specific order. Lastly, you can also simply wait for the synchronization to start automatically: in six hours, or in any other time defined as repo_sync_frequency in /etc/rhui/rhui-tools.conf.

   Important

   In any case, the repositories will not be available in the meantime.