SUU Missing Support for RHEL 8

Hi eddierowe

I completely understand your frustration. When you have a reliable workflow for managing a fleet of systems, unexpected changes to tool compatibility can be a major headache.

Why was RHEL 8 support removed from SUU?
The technical reason stems from architectural changes in Red Hat Enterprise Linux 8 and Dell's strategic shift in update delivery. RHEL 8 deprecated or completely removed several legacy 32-bit libraries, legacy shell environments, and dependencies that the traditional, monolithic Server Update Utility (SUU) relied upon to execute its GUI and inventory scripts. Rather than rebuilding the legacy SUU framework to support modern Linux distributions, Dell shifted its focus toward native Linux package management and out-of-band management tools, which are generally more secure and lightweight.

Reliable Alternatives to SUU (Excluding Dell Repository Manager)
Since you manage a fleet and want to avoid DRM entirely, here are the most reliable, Dell-supported alternatives for keeping your systems up to date:

1. Dell System Update (DSU)
If you prefer to run updates locally from within the operating system (similar to how you used SUU), DSU is the direct replacement.

• How it works: It is a native, CLI-based deployment tool optimized for Linux. You can install it on RHEL 8 via the Dell Linux repository.
• Why it's good: It uses native RPM packages, handles dependencies automatically, and can be easily scripted across your fleet using Ansible, Bash, or your configuration management tool of choice. You can point it directly to Dell's online catalog to pull the latest updates without needing a localized repository.

2. iDRAC and Lifecycle Controller (Out-of-Band Updates)
For fleet management, moving updates out of the OS layer entirely is often the most reliable method, as it eliminates OS dependency issues (like the RHEL 8 SUU issue) altogether.

• How it works: You can update systems directly via the iDRAC by pointing it to downloads.dell.com (via HTTPS) or an internal network share (HTTP/HTTPS/NFS/CIFS).
• Why it's good: You can script this across your fleet using RACADM CLI commands or Redfish APIs. A simple Redfish POST request can instruct the iDRAC to reach out to Dell's servers, download the necessary firmware, and apply it on the next reboot.

3. OpenManage Enterprise (OME)
Since you are managing a fleet of servers, OpenManage Enterprise is Dell's primary console for this.

• How it works: OME is a free virtual appliance you deploy in your environment. It connects to your servers out-of-band via iDRAC.
• Why it's good: It can automatically pull the latest update catalogs directly from Dell. You can group your servers, run compliance reports to see what is out of date, and schedule firmware updates to happen silently during your maintenance windows. It completely removes the need to manually mount ISOs or run local OS scripts.

Recommendation:
If you want to stick to an in-OS scriptable method, DSU is going to be your best and most reliable bet for RHEL 8. If you are open to moving away from in-OS updates entirely, automating updates via iDRAC/Redfish or setting up OpenManage Enterprise will likely save you the most time in the long run.