Chapter 7. March 2026
Review the March 2026 updates and fixes for Red Hat Lightspeed.
7.1. Product-wide updates
Review the March 2026 product-wide updates for Red Hat Lightspeed.
- Published blogs and resources
- Interactive demo: Ask Claude about RHEL lifecycle and planning through Red Hat Lightspeed MCP by Samiksha Saxena (March 18, 2026)
- Interactive demo: Get your top vulnerabilities information through Claude by Samiksha Saxena (March 18, 2026)
7.2. Red Hat Enterprise Linux updates
Review the March 2026 updates and fixes for Red Hat Lightspeed running on RHEL systems.
7.2.1. Inventory
- UI enhancements and fixes
- Added copy to clipboard actions (copy icon) on the System Properties and Data Collectors cards on the System Details page. You can now copy values such as host names and IDs.
- Renamed the Patch tab to Content on the System Details page to improve consistency across the console.
- Removed restrictions that prevented hosts within a workspace from reassignment, so that you can move systems between workspaces more flexibly.
- Introduced a Move system action to streamline workspace reassignment.
- Resolved a Sentry error when you apply tag filters in inventory. Before this update, a Sentry error occurred when you applied those filters.
- API improvements
Fixed host filtering on the
/hostsendpoint so that it accepts JSON notation in thefilter[system_profile]query parameter.-
Before this update, those requests failed with
500errors.
-
Before this update, those requests failed with
7.2.2. Remediations
- Remediations API scalability and performance updates
- In a single remediations API call, you can add at most 100 issues and 100 distinct systems to a remediation plan.
When you generate a playbook, the API finds issues in more detail and returns errors more consistently.
For more information, see Red Hat Lightspeed Remediations API Change Log.
- Planned remediations in execution readiness
When you create a remediation plan, Red Hat Lightspeed now uses a system of action points to support reliable performance without timeouts or failures. Action points calculate the relative complexity and performance impact of a remediation plan. This update helps you decide how and where to execute the plan. Complex issues require a higher number of action points, and simpler issues require a lower number.
Red Hat Lightspeed assigns a specific point value to each type of issue and calculates the plan’s total size against the platform’s performance capabilities.
Issue types use the following action point weights:
- Vulnerability: 20 action points per system
- Advisor: 20 action points per system
- Compliance: 5 action points per system
- Patch: 2 action points per system
- Red Hat Lightspeed supports reliable execution for plans up to 1000 action points and 100 systems.
- Streamlined single-page plan creation
- The multi-step wizard for creating a remediation plan in Red Hat Lightspeed has been replaced by a single-page modal. You now name your plan, configure auto-reboot settings, and download or view the Ansible Playbook from one screen.
- Multiple resolution selection
- Previously, when creating a plan with multiple resolution options, you had to choose a remediation approach before creating the plan. You can now compare choices and select the best fit after you have created your remediation plan. You find the available remediation options on the Plan details tab of your plan under the Multiple resolutions section.
- UI enhancements and fixes for planned remediations
- The Actions and Systems tabs have been merged into a unified Planned Remediations tab. This tab adds a graphical view of the plan’s systems and action points.
- The Systems table includes new connection troubleshooting modals. These modals provide step-by-step CLI and Satellite commands to reconnect hosts based on subscription type.
- The revised execution confirmation popover presents the confirmation details more clearly.
7.2.3. Advisor
- Access new recommendations, included with your Red Hat subscription.
-
Input latency occurs in the GUI when the
mutter-40.9.el9_6_1package is installed. -
Kernel panic occurs because of a
NULLpointer dereference in the CIFS module when you runsos report - Performance degradation occurs when the TSC clocksource unexpectedly switches
-
Device-mapper deadlocks cause a system hang by leading to a stuck
multipathdprocess and an I/O flush failure -
The NFS server crashes at
nfsd4_cb_donebecause of a known issue in thenfsdmodule - Red Hat Enterprise Linux 7 hosts fail to register with Red Hat Satellite running on Red Hat Enterprise Linux 9 when FIPS mode is enabled
- GFS2 withdrawal occurs while you access the file system
-
Processes that use pNFS can become blocked when the
nfs_layout_nfsv41_filesmodule is loaded -
Memory leak occurs when the
icedriver is loaded and legacy-rx is off -
The
systemdservice cannot attach cgroups for the user manager because the service restarts too rapidly -
Initramfsgeneration fails because of a corrupt/etc/pki/tls/openssl.cnffile - Red Hat does not provide technical support services or software maintenance services for Python
-
Input latency occurs in the GUI when the
7.2.4. Content templates (Patch)
- RHEL 10 extension repositories are available in content templates
- You can add the Red Hat Enterprise Linux 10 extensions repository to content templates for patching and image building with those packages. The Red Hat Enterprise Linux 10 extensions repository includes hardware acceleration drivers from partners such as NVIDIA and AMD.
7.2.5. Subscriptions
- New subscriptions notifications for exceeded utilization threshold
Red Hat Lightspeed includes a new Subscriptions service event type that notifies you when subscription usage exceeds defined capacity thresholds. The Exceeded Utilization Threshold event gives proactive visibility into capacity overruns and helps you identify compliance risks and take corrective action before you reach subscription limits.
The event integrates with the Hybrid Cloud Console Notifications service and follows the standard event schema. You can use it alongside other Red Hat Lightspeed events for operational monitoring and cost management. You can also forward alerts to external systems such as Splunk, ServiceNow, or Slack. You can also trigger automated workflows such as Event-Driven Ansible.
7.2.6. Image builder
- Blueprint-defined user groups
-
You can define user groups and assign users to them in the blueprint creation wizard. Each group receives a default UID that you can edit. Before this update, you could add users only to default groups, such as
wheel.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}