Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 3. February 2026

Review the February 2026 updates and fixes for Red Hat Lightspeed.

3.1. Product-wide updates
Link kopieren

Published blogs and resources

3.2. Red Hat Enterprise Linux updates
Link kopieren

Review the February 2026 updates and fixes for Red Hat Lightspeed running on RHEL systems.

3.2.1. Inventory
Link kopieren

UI fixes and improvements
  • Reset to default button is now disabled when the selected staleness value already matches the system default.
  • The Edit button is now hidden in the editing mode to prevent conflicting actions.
  • The Save button is now disabled when there are no changes made in the Staleness form, preventing accidental submissions.
  • Validation error messages now include an Error: prefix for clarity.
  • Validation error text now has danger red color for better visibility.
  • Improved icon alignment within popovers for better visual consistency.
  • Improved Workspaces and Staleness/Deletion popovers for a more intuitive experience.
  • Added missing space in the Workspaces no-access empty state message.
API Improvements
  • Inventory hosts endpoint now return failed IDs in 404 responses when querying /hosts/<id list>, making error handling easier.
  • Fixed support for JSON array syntax in the fields query parameter on the /hosts API to match documented behavior.
System Details Page Updates
  • Consolidated system information into clearer categories across the Details and Overview tabs.
  • Long hostnames in the System Properties card now truncate for cleaner display.
  • Inventory now displays AI model information for RHEL AI systems, providing richer system insight.
  • Data Collectors card updated with state icons and simplified layout by removing expanded items.

3.2.2. Remediations
Link kopieren

API scalability and performance updates
  • The number of issues and systems that can be added to a remediation plan in a single remediation API call is now limited to a maximum of 50 issues per API call and 50 distinct systems per API call.
  • GET /remediations/:id/playbook returns 204 No Content when a plan has no systems. Previously it was 404 error message.
  • Added more granular issue reporting and improved error handling consistency for playbook generation.

3.2.3. Advisor
Link kopieren

New recommendations released

3.2.4. Image builder
Link kopieren

New image build targets
  • Network installer images are analogous to the Boot ISO images. They are available from the customer portal and include information to launch an installer for additional configuration and package installation. A network connection to package repositories is required for successful installation.
  • Preboot Execution Environment (PXE) boot images, which are sometimes referred to as stateless or diskless images, are minimal archives that include the kernel, intramfs, and root file system needed to boot a system over the network. These images are popular for the Satellite provisioning and for high performance compute nodes.
Extended retention policy for built images
Customers can now access downloadable images for up to seven days, extended from the previous six hours. This change is helpful for users who might start a build and come back to it later or users who are building the image for someone else to download.
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2026 Red HatNach oben