mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Enhancements This section describes the major enhancements introduced in Red Hat OpenShift Data foundation 4.17. 3.1. Capacity consumption trend card Consumption trend card in OpenShift Data Foundation dashboard provides information about the estimated days until the storage is full and this helps in new hardware procurement. Storage consumption rate is calculated based on the actual capacity utilization, historical usage, and current consumption rate and is displayed in GiB per day. The number of days left for the storage to reach the threshold capacity is also shown. For more information, see Metrics in the Block and File dashboard . 3.2. Bucket logging and log based replication optimization for Multicloud Object Gateway buckets Supports replication of large amounts of data between Multicloud Object Gateway (MCG) and Amazon Web Services (AWS) or MCG and MCG. The support for log-based replication for AWS S3 using bucket logging is extended to MCG bucket for optimization. The log-based replication optimization also supports object prefix filtering. For more information, see Bucket logging for Multicloud Object . 3.3. Capacity alert thresholds increased The thresholds of the PersistentVolumeUsageCritical and PersistentVolumeUsageNearFull alerts are increased so that they are triggered only when the space is limited. Previously, these PersistentVolumeUsageCritical and PersistentVolumeUsageNearFull alerts that were triggered even when there was still plenty of space available caused unnecessary worry about the state of the cluster. 3.4. Ceph full thresholds configurations The Ceph OSD full thresholds can be set using the ODF CLI tool or by updating the StorageCluster CR. For more information, see Setting Ceph OSD full thresholds by updating the StorageCluster CR . 3.5. Preserve the CLI flags that were passed during creation of external clusters The command-line interface (CLI) flags passed during creation can be preserved during upgrade automatically. Passing the new flags during upgrade helps to use additional features. For more information, see Creating an OpenShift Data Foundation Cluster for external Ceph storage system . 3.6. MDS scalability Multiple active metadata services (MDS) can be run when MDS CPU usage becomes too high. For more information, see the Troubleshooting guide . 3.7. Traditional user experience for must gather utility In versions, running must-gather required an < -arg> flag to specify which logs to collect. With this update, must-gather no longer requires a < -arg> flag, and by default collects all logs. 3.8. CephCSI pod log rotation Log rotation of CephCSI pods is enabled with csi-operator so client operator can use it. 3.9. topologySpreadConstraints added to PV backingstore pods so they get scheduled on a spread basis Previously, when a PV backingstore was created, the backingstore pod was scheduled randomly on any node. This was not ideal because if any node went down, all the backingstore pods on that node would go down as well. To increase high availability, a topology spread constraint is added to the backingstore pod so that they get scheduled on a spread basis.

Commands:
Chapter 10. Known issues in Red Hat Decision Manager 7.13.2 This section lists known issues with Red Hat Decision Manager 7.13.2. 10.1. Red Hat OpenShift Container Platform PostgreSQL 13 Pod won't start because of an incompatible data dirctory [ RHPAM-4464 ] Issue: When you start a PostgreSQL pod after you upgrade the operator, the pod fails to start and you receive the following message: Incompatible data directory. This container image provides PostgreSQL '13', but data directory is of version '10'. This image supports automatic data directory upgrade from '12', please carefully consult image documentation about how to use the 'USDPOSTGRESQL_UPGRADE' startup option. Workaround: Check the version of PostgreSQL: If the PostgreSQL version returned is 12.x or earlier, upgrade PostgreSQL: Red Hat Decision Manager version PostgreSQL version Upgrade instructions 7.13.1 7.10 Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x. 7.13.2 7.10 1. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 12.x. 2. Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x. 7.13.2 7.12 Follow the instructions in Upgrading database (by switching to newer PostgreSQL image version) to upgrade to PostgreSQL 13.x. Verify that PostpreSQL has been upgraded to your required version:

Commands:
postgres -V
postgres -V
Chapter 3. Bug fixes 3.1. CodeReady Workspaces with the CodeReady Workspaces server engine and GitHub OAuth successfully starts devfile v2 workspaces Before this update, when a CodeReady Workspaces instance was configured with the CodeReady Workspaces server engine and GitHub OAuth, CodeReady Workspaces failed to start a workspace using the devfile v2 specification. With this update, a CodeReady Workspaces instance configured with the CodeReady Workspaces server engine and GitHub OAuth successfully starts a workspace using the devfile v2 specification. Additional resources CRW-2705

Commands:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 8 release of Eclipse Temurin includes, see OpenJDK 8u412 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements that the Eclipse Temurin 8.0.412 release provides: Kerberos 5 replay cache interoperability with MIT krb5-1.15 In OpenJDK 8.0.412, the Kerberos 5 replay cache file ( rcache ) uses the SHA256 algorithm. This supersedes the behavior in releases where rcache used the MD5 algorithm. The Massachusetts Institute of Technology (MIT) Kerberos 5 Release 1.15 (krb5-1.15) also uses the SHA256 algorithm, which is interoperable with earlier releases of MIT krb5. If you want to continue using the MD5 algorithm, ensure that the new system property jdk.krb5.rcache.useMD5 is set to true . The MD5 algorithm is useful in the following situations: If your system has a coarse clock and depends on hash values in replay attack detection If your system needs to interoperate with the rcache files in older OpenJDK releases See JDK-8168518 (JDK Bug System) . SystemTray.isSupported() method returns false on most Linux desktops In OpenJDK 8.0.412, the java.awt.SystemTray.isSupported() method returns false on systems that do not support the SystemTray API correctly. This enhancement is in accordance with the SystemTray API specification. The SystemTray API is used to interact with the taskbar in the system desktop to provide notifications. SystemTray might also include an icon representing an application. Due to an underlying platform issue, GNOME desktop support for taskbar icons has not worked correctly for several years. This platform issue affects the JDK's ability to provide SystemTray support on GNOME desktops. This issue typically affects systems that use GNOME Shell 44 or earlier. Note Because the lack of correct SystemTray support is a long-standing issue on some systems, this API enhancement to return false on affected systems is likely to have a minimal impact on users. See JDK-8322750 (JDK Bug System) . Certainly R1 and E1 root certificates added In OpenJDK 8.0.412, the cacerts truststore includes two Certainly root certificates: Certificate 1 Name: Certainly Alias name: certainlyrootr1 Distinguished name: CN=Certainly Root R1, O=Certainly, C=US Certificate 2 Name: Certainly Alias name: certainlyroote1 Distinguished name: CN=Certainly Root E1, O=Certainly, C=US See JDK-8321408 (JDK Bug System) . Revised on 2024-04-26 14:39:29 UTC

Commands:
Chapter 26. Sessions limits Setting a session limit enables administrators to limit the number of simultaneous sessions per user or per IP address. 26.1. Working with session limits In automation controller, a session is created for each browser that a user logs in with. This forces the user to log out of any extra sessions after they exceed the administrator-defined maximum. Session limits can be important, depending on your setup. Example You only want a single user on your system with a single login per device (where the user can log in on their work laptop, phone, or home computer). In this case, you want to create a session limit equal to 1 (one). If the user logs in on their laptop, for example, then logs in using their phone, their laptop session expires (times out) and only the login on the phone persists. Proactive session limits kick the user out when the session is idle. The default value is -1 , which disables the maximum sessions allowed. This means that you can have as many sessions without an imposed limit. While session counts can be very limited, you can also expand them to cover as many session logins as are needed by your organization. When a user logs in resulting in other users being logged out, the session limit has been reached and those users who are logged out are notified as to why the logout occurred. Procedure To make changes to your session limits, from the navigation panel, select Settings . Select Miscellaneous Authentication settings from the list of System options. Click Edit . Edit the Maximum number of simultaneous logged in sessions setting or use the Browsable API if you are comfortable with making REST requests. Note To make the best use of session limits, disable AUTH_BASIC_ENABLED by changing the value to false , as it falls outside the scope of session limit enforcement. Alternatively, in the Miscellaneous Authentication settings , toggle the Enable HTTP Basic Auth to off.

Commands:
4.160. lohit-kannada-fonts 4.160.1. RHEA-2011:1140 - lohit-kannada-fonts enhancement update An updated lohit-kannada-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-kannada-fonts package provides a free Kannada TrueType/OpenType font. Enhancement BZ# 691289 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-kannada-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
7.299. coreutils 7.299.1. RHBA-2013:0703 - coreutils bug fix update Updated coreutils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The coreutils package contains the core GNU utilities. It is a combination of the old GNU fileutils, sh-utils, and textutils packages. Bug Fix BZ# 924711 The "tail -f" command uses inotify for tracking changes in files. For remote file systems [-/,] inotify is not available. In the case of unknown file systems, for example panasas, "tail -f" failed instead of falling back to polling. Now, the list of known file systems is updated and "tail -f" is modified to fall back into polling for unknown file systems. As result, "tail -f" now works correctly, even on unknown file systems, with only a warning about the unknown file system and a fall back to polling. Users of coreutils are advised to upgrade to these updated packages, which fix this bug. 7.299.2. RHBA-2013:0858 - coreutils bug fix update Updated coreutils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The coreutils package contains the core GNU utilities. It is a combination of the old GNU fileutils, sh-utils, and textutils packages. Bug Fix BZ# 963327 When parsing the file content and the end of a field was specified using the obsolete key formats (+POS -POS), the sort utility determined the end of the field incorrectly, and therefore produced incorrect output. This update fixes the parsing logic to match the usage of the "-k" option when using these obsolete key formats. The sort utility now returns expected results in this situation. Users of coreutils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Fixed issues CVE-2020-7656 - jquery: allows XSS via the load method [amq-ic-1] The issue has been resolved by updating the jQuery dependency. CVE-2020-11022 - jquery: Cross-site scripting due to improper injQuery.htmlPrefilter method [amq-ic-1] The issue has been resolved by updating the jQuery dependency. CVE-2020-11023 - jquery: passing HTML containing <option> elements to manipulation methods could result in untrusted code execution [amq-ic-1] The issue has been resolved by updating the jQuery dependency. ENTMQIC-2446 - Router crash with epoll error EPOLL_CTL_DEL Previously, the router could crash due to a race condition. The issue has been resolved. ENTMQIC-2485 - The VhostNamePatterns does not work in OCP env Previously, using # in the hostname of a vhost policy did not set the policy correctly. The issue has been fixed. ENTMQIC-2481 - Unable to delete listener with http enabled Previously, if you created a listener with http set to true you could not later delete that listener. The issue has been fixed. ENTMQIC-2460 - Adding new config address, autolinks and link routes become slower as more get added Previously, if you created many addresses the creation of more addresses becomes slow. The issue has been fixed.

Commands:
7.228. slapi-nis 7.228.1. RHBA-2013:0370 - slapi-nis bug fix update An updated slapi-nis package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The slapi-nis package contains the NIS server plug-in and the Schema Compatibility plug-in for use with the 389 directory server. Bug Fixes BZ# 840926 While updating their internal data caches after the server had processed an LDAP modify request, the modules leaked a small amount of memory after every modify request. This bug has been fixed and no memory is now leaked in the described scenario. BZ# 829502 At build-time, the slapi-nis package attempted to detect if it was being built for a version of the directory server which included support for backend transactions. If this support was detected, the plug-in enabled its own optional logic for supporting transactions in order to allow it to interact properly with the server and other plug-ins. Some time after this support was added to slapi-nis, the recommended strategy for integrating with a transaction-enabled server was revised, rendering changes in slapi-nis incorrect. This update explicitly disables that support in these plug-in, thus preventing this support from interfering with normal directory server operations. Users of slapi-nis are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 2. Red Hat OpenStack Platform certification targets You are expected to implement the following targets achieve a certification: 2.1. Products implementing OpenStack APIs This category includes products that deliver an OpenStack service/functionality such as launching server instances, adding new routers, creating images, creating storage containers and objects, creating user profiles, etc. by implementing an API and/or an API Extension for Networking, Block Storage, or File Share services. For products implementing OpenStack APIs, you need to successfully complete the relevant certification tests for the API group in addition to the OpenStack Director test ( openstack/director ) and OpenStack Supportability tests ( openstack/supportable ). To ensure that the underlying platform is supported by Red Hat, run the OpenStack Director, Supportability, and sosreport tests on multiple overcloud nodes. The test results should be from a controller, and a compute or storage nodes implementing/consuming Openstack APIs that the vendor plugin controls. Important It is your responsibility to ensure these tests are run on the correct nodes. Additional runs may be requested to fulfill these requirements. In this case, the certification process verifies that the service delivers the API according to the platform specification and that the underlying OpenStack environment is configured correctly. 2.2. Products consuming OpenStack APIs This category covers all products/applications that rely on OpenStack services (like Networking, Block Storage, File Share etc.) to operate. Such products generally facilitate an OpenStack deployment or complement the Cloud Infrastructure with additional functionalities such as configuration, scaling, and management. Examples OpenStack management and orchestration applications like Network Functions Virtualization Management and Orchestration (NFV MANO) OpenStack monitoring applications Other OpenStack-enabled applications such as virtual network functions (VNFs) For such applications, you need to successfully complete the OpenStack Director test ( openstack/director ) and OpenStack Supportability tests ( openstack/supportable ). 2.3. Support for certified OpenStack component Support for certified Openstack components such as plugins/drivers and customer assistance is derived from the vendor that is shipping the component. If Red Hat certifies and ships a third-party component as part of RHOSP and there is a question or issue with that component, the customers will contact Red Hat for assistance. If a third-party ships a RHOSP-certified component and there is a question or issue with that component, the third party will be fully responsible for assisting the customer and providing support for that component. However, Red Hat certified Partners and Red Hat, maintain active engineering relationships that either party can leverage to ensure quick progress is made on customer issues. Additional Resources For more information on supportability of RHOSP certified components, see article .

Commands:
Part II. Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.4 Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. Starting with this release, the distribution files for Red Hat Decision Manager are replaced with Red Hat Process Automation Manager files. There are no Decision Manager artifacts. The Red Hat Decision Manager subscription, support entitlements, and fees remain the same. Red Hat Decision Manager subscribers will continue to receive full support for the decision management and optimization capabilities of Red Hat Decision Manager. The business process management (BPM) capabilities of Red Hat Process Automation Manager are exclusive to Red Hat Process Automation Manager subscribers. They are available for use by Red Hat Decision Manager subscribers but with development support services only. Red Hat Decision Manager subscribers can upgrade to a full Red Hat Process Automation Manager subscription at any time to receive full support for BPM features. This document describes how to install Red Hat Process Automation Manager on a Red Hat JBoss Enterprise Application Platform 7.4 instance. Prerequisites You have reviewed the information in Planning a Red Hat Decision Manager installation . You have installed the latest patch release of Red Hat JBoss Enterprise Application Platform 7.4. For information about installing Red Hat JBoss EAP, see the Red Hat JBoss Enterprise Application Platform installation guide .

Commands:
Chapter 8. Compliance and Vulnerability Scanning with OpenSCAP 8.1. Security Compliance in Red Hat Enterprise Linux A compliance audit is a process of figuring out whether a given object follows all the rules written out in a compliance policy. The compliance policy is defined by security professionals who specify desired settings, often in the form of a checklist, that are to be used in the computing environment. The compliance policy can vary substantially across organizations and even across different systems within the same organization. Differences among these policies are based on the purpose of these systems and its importance for the organization. The custom software settings and deployment characteristics also raise a need for custom policy checklists. Red Hat Enterprise Linux provides tools that allow for fully automated compliance audit. These tools are based on the Security Content Automation Protocol (SCAP) standard and are designed for automated tailoring of compliance policies. Security Compliance Tools Supported on Red Hat Enterprise Linux 6 OpenSCAP - The oscap command-line utility is designed to perform configuration and vulnerability scans on a local system, to validate security compliance content, and to generate reports and guides based on these scans and evaluations. Script Check Engine (SCE) - SCE is an extension to SCAP protocol that allows content authors to write their security content using a scripting language, such as Bash, Python or Ruby. The SCE extension is provided with the openscap-engine-sce package. SCAP Security Guide (SSG) - The scap-security-guide package provides the latest collection of security polices for Linux systems. If you require performing automated compliance audits on multiple systems remotely, you can utilize OpenSCAP solution for Red Hat Satellite. For more information see Section 8.5, "Using OpenSCAP with Red Hat Satellite" and Section 8.8, "Additional Resources" . Note Note that Red Hat does not provide any default compliance policy along with the Red Hat Enterprise Linux 6 distribution. The reasons for that are explained in Section 8.2, "Defining Compliance Policy" .

Commands:
Chapter 1. Boot Process, Init, and Shutdown An important and powerful aspect of Red Hat Enterprise Linux is the open, user-configurable method it uses for starting the operating system. Users are free to configure many aspects of the boot process, including specifying the programs launched at boot-time. Similarly, system shutdown gracefully terminates processes in an organized and configurable way, although customization of this process is rarely required. Understanding how the boot and shutdown processes work not only allows customization, but also makes it easier to troubleshoot problems related to starting or shutting down the system. 1.1. The Boot Process Below are the basic stages of the boot process for an x86 system: The system BIOS checks the system and launches the first stage boot loader on the MBR of the primary hard disk. The first stage boot loader loads itself into memory and launches the second stage boot loader from the /boot/ partition. The second stage boot loader loads the kernel into memory, which in turn loads any necessary modules and mounts the root partition read-only. The kernel transfers control of the boot process to the /sbin/init program. The /sbin/init program loads all services and user-space tools, and mounts all partitions listed in /etc/fstab . The user is presented with a login screen for the freshly booted Linux system. Because configuration of the boot process is more common than the customization of the shutdown process, the remainder of this chapter discusses in detail how the boot process works and how it can be customized to suite specific needs.

Commands: