mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Preparing to deploy OpenShift Container Storage Deploying OpenShift Container Storage on OpenShift Container Platform using dynamic storage devices provides you with the option to create internal cluster resources. This will result in the internal provisioning of the base services, which helps to make additional storage classes available to applications. Before you begin the deployment of Red Hat OpenShift Container Storage, follow these steps: Optional: If you want to enable cluster-wide encryption using an external Key Management System (KMS): Ensure that a policy with a token exists and the key value backend path in Vault is enabled. See Enabling the key value backend path and policy in Vault . Ensure that you are using signed certificates on your Vault servers. Minimum starting node requirements [Technology Preview] An OpenShift Container Storage cluster will be deployed with minimum configuration when the standard deployment resource requirement is not met. See Resource requirements section in Planning guide. 1.1. Enabling key value backend path and policy in Vault Prerequisites Administrator access to Vault. Choose a unique path name as the backend path that follows the naming convention since it cannot be changed later. Procedure Enable the Key/Value (KV) backend path in Vault. For Vault KV secret engine API, version 1: For Vault KV secret engine API, version 2: Create a policy to restrict users to perform a write or delete operation on the secret using the following commands: Create a token matching the above policy:

Commands:
vault secrets enable -path=ocs kv
vault secrets enable -path=ocs kv-v2
echo ' path "ocs/*" { capabilities = ["create", "read", "update", "delete", "list"] } path "sys/mounts" { capabilities = ["read"] }'| vault policy write ocs -
vault token create -policy=ocs -format json
Chapter 1. New and changed features Note This release introduces new minimum required versions for C++, Java, and Python: C++11, Java 11, and Python 3.6. For more information, see Red Hat AMQ 7 Supported Configurations . Note This release enables SSL/TLS hostname and certificate verification by default in the Python and Ruby clients. This matches the existing behavior of the C++, JMS, and .NET clients. 1.1. AMQ C++ ENTMQCL-1083 - Application properties for links The C++ client now offers the ability to query and set application-specfic properties on AMQP links. 1.2. AMQ Python and AMQ Ruby ENTMQCL-2961 - Enable SSL/TLS host verification by default The Python and Ruby clients now enable SSL/TLS hostname and certificate verification by default. This matches the existing behavior of the C++, JMS, and .NET clients.

Commands:
Chapter 9. Installing the load balancer The following example provides general guidance for configuring an HAProxy load balancer using Red Hat Enterprise Linux 9 or Red Hat Enterprise Linux 8. However, you can install any suitable load balancing software solution that supports TCP forwarding. Procedure Install HAProxy: Install the following package that includes the semanage tool: Configure SELinux to allow HAProxy to bind any port: Configure the load balancer to balance the network load for the ports as described in Table 9.1, "Ports configuration for the load balancer" . For example, to configure ports for HAProxy, edit the /etc/haproxy/haproxy.cfg file to correspond with the table. For more information, see Configuration example for haproxy.cfg for HAProxy load balancer with Satellite 6 in the Red Hat Knowledgebase . Table 9.1. Ports configuration for the load balancer Service Port Mode Balance Mode Destination HTTP 80 TCP roundrobin port 80 on all Capsule Servers HTTPS and RHSM 443 TCP source port 443 on all Capsule Servers Anaconda for template retrieval 8000 TCP roundrobin port 8000 on all Capsule Servers Puppet ( Optional ) 8140 TCP roundrobin port 8140 on all Capsule Servers PuppetCA ( Optional ) 8141 TCP roundrobin port 8140 only on the system where you configure Capsule Server to sign Puppet certificates Capsule HTTPS for Host Registration and optionally OpenSCAP 9090 TCP roundrobin port 9090 on all Capsule Servers Configure the load balancer to disable SSL offloading and allow client-side SSL certificates to pass through to back end servers. This is required because communication from clients to Capsule Servers depends on client-side SSL certificates. Start and enable the HAProxy service:

Commands:
dnf install haproxy
dnf install policycoreutils-python-utils
semanage boolean --modify --on haproxy_connect_any
systemctl enable --now haproxy
Chapter 8. MTR 1.2.1 8.1. Known issues For a complete list of all known issues, see the list of MTR 1.2.1 known issues in Jira. 8.2. Resolved issues CVE-2023-44487 netty-codec-http2: HTTP/2 Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack). The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly. (WINDUP-4056) For a complete list of all issues resolved in this release, see the list of MTR 1.2.1 resolved issues in Jira.

Commands:
16.13. Troubleshooting A test tool is available to check that libguestfs is working. Run the following command after installing libguestfs (root access not required) to test for normal operation: This tool prints a large amount of text to test the operation of libguestfs. If the test is successful, the following text will appear near the end of the output:

Commands:
libguestfs-test-tool
===== TEST FINISHED OK =====
22.14. Configure the Firewall to Allow Incoming NTP Packets The NTP traffic consists of UDP packets on port 123 and needs to be permitted through network and host-based firewalls in order for NTP to function. 22.14.1. Configure the Firewall Using the Graphical Tool To enable NTP to pass through the firewall, using the graphical tool system-config-firewall , issue the following command as root: The Firewall Configuration window opens. Select Other Ports from the list on the left. Click Add . The Port and Protocol window opens. Click on one of the port numbers and start typing 123 . Select the " port 123 " entry with udp as the protocol. Click OK . The Port and Protocol window closes. Click Apply in the Firewall Configuration window to apply the changes. A dialog box will pop up to ask you to confirm the action, click Yes . Note that any existing sessions will be terminated when you click Yes .

Commands:
~]# system-config-firewall
B.31.4. RHSA-2010:0873 - Critical: java-1.5.0-ibm security update Updated java-1.5.0-ibm packages that fix several security issues are now available for Red Hat Enterprise Linux 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM 1.5.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2010-1321 , CVE-2010-3541 , CVE-2010-3548 , CVE-2010-3549 , CVE-2010-3550 , CVE-2010-3551 , CVE-2010-3556 , CVE-2010-3559 , CVE-2010-3562 , CVE-2010-3565 , CVE-2010-3566 , CVE-2010-3568 , CVE-2010-3569 , CVE-2010-3572 , CVE-2010-3573 , CVE-2010-3574 This update fixes several vulnerabilities in the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. All users of java-1.5.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.5.0 SR12-FP2 Java release. All running instances of IBM Java must be restarted for this update to take effect.

Commands:
probe::vm.pagefault.return Name probe::vm.pagefault.return - Indicates what type of fault occurred. Synopsis Values name Name of the probe point fault_type Returns either 0 (VM_FAULT_OOM) for out of memory faults, 2 (VM_FAULT_MINOR) for minor faults, 3 (VM_FAULT_MAJOR) for major faults, or 1 (VM_FAULT_SIGBUS) if the fault was neither OOM, minor fault, nor major fault.

Commands:
vm.pagefault.return
7.23. cifs-utils 7.23.1. RHBA-2015:1366 - cifs-utils bug fix update Updated cifs-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Server Message Block/Common Internet File System (SMB/CIFS) protocol is a standard file sharing protocol widely deployed on Microsoft Windows machines. The cifs-utils packages contain tools for mounting shares on Linux using the SMB/CIFS protocol. The tools in this package work in conjunction with support in the kernel to enable mounting a SMB/CIFS share onto a client and use it as if it were a standard Linux file system. Bug Fix BZ# 1080482 Previously, attempts to mount a CIFS share failed when the system keytab was stored in a non-default location specified using the default_keytab_name setting in the /etc/krb5.conf file, even when the user provided the correct Kerberos credentials. However, mounting succeeded when default_keytab_name pointed to the default /etc/krb5.keytab file. The cifs.upcall helper process has been modified to respect non-default keytab locations provided using default_keytab_name. As a result, CIFS mount now works as expected even when the keytab is stored in a non-default location. Users of cifs-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.33. corosync 8.33.1. RHBA-2014:1508 - corosync bug fix update Updated corosync packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. This update also fixes the following bugs: Note The corosync packages have been upgraded to upstream version 1.4.7, which provides a number of bug fixes over the version. (BZ# 1055584 ) This update also fixes the following bugs: Bug Fixes BZ# 1067043 If the cpg clients on active cluster nodes terminated while corosync on one of the nodes was paused, corosync did not update its internal information about cpg clients on other nodes properly after resuming. Consequently, that node considered the terminated cgp clients to be still up and running. This update modifies the cpg code to ensure that corosync properly updates information about the cpg membership in this situation. BZ# 1011307 Previously, corosync terminated unexpectedly with a segmentation fault when started on a system with the /dev/shm device full. This happened because the corosync logging system, logsys, could not be properly initialized. This update improves handling of the logsys initialization, and corosync now displays an appropriate error message and exits gracefully if logsys cannot be initialized. BZ# 1025321 Due to a list corruption bug in the Corosync Closed Process Group (CPG) API, corosync could terminate unexpectedly with a segmentation fault under some circumstances. To fix this problem, corosync has been modified to handle the CPG init and list removal functions in the same thread. BZ# 1005179 Previously, corosync could abort without logging an error properly if it was unable to store a file to the user's file system. With this update, corosync now properly verifies whether a "blackbox" can be stored on the file system. A failure of a ring ID store operation is no longer handled by assert but corosync now tries to log an error and then exits gracefully. BZ# 1001210 Previously, when using the InfiniBand Architecture (IBA) as a transport protocol for corosync, corosync could not properly handle the restart of the IBA subnet manager (SM). If the IBA SM was restarted, corosync was not able to start or became unresponsive if it was already running. A series of patches addressing this problem has been applied to corosync, and it now works properly as expected in this scenario. The corosync packages have been upgraded to upstream version 1.4.7, which provides a number of bug fixes over the version. (BZ#1055584) Users of corosync are advised to upgrade to these updated packages, which fix these bugs.

Commands:
5.162. libuser 5.162.1. RHBA-2012:0455 - libuser bug fix update Updated libuser packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The libuser library implements a standardized interface for manipulating and administering user and group accounts. The library uses pluggable back-ends to interface to its data sources. Sample applications modeled after those included with the shadow password suite are included. Bug Fixes BZ# 670151 When creating a user account in Lightweight Directory Access Protocol (LDAP), the libuser library used the value of the "gecos" attribute as the default value of the "cn" attribute. When the "gecos" attribute was empty, this made the value of "cn" invalid, and the creation of the user account failed. With this update, the user name of the account is stored in the "cn" attribute if the "gecos" attribute is empty, thus allowing successful creation of the user account. BZ# 724987 When populating a home directory by copying files from the /etc/skel directory, libuser ignored the "set user-id" and "set group-id" flags. This made it impossible to set up group-shared directories in a home directory. With this update, the "set user-id" and "set group-id" flags are preserved. BZ# 788521 Previously, when searching for the user or group account information in files of certain sizes, the libuser library could terminate unexpectedly with a segmentation fault. A patch has been applied to address this issue, and crashes no longer occur in the aforementioned scenario. All users of libuser are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.54. evolution-data-server 8.54.1. RHBA-2014:1418 - evolution-data-server bug fix and enhancement update Updated evolution-data-server packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The evolution-data-server packages provide a unified back end for applications which interact with contacts, task and calendar information. Evolution Data Server was originally developed as a back end for Evolution, but is now used by various other applications. Bug Fix BZ# 1040178 Due to incorrect locking of table access, Evolution previously became unresponsive on startup. This update fixes locking of table access, and Evolution now starts up as intended. In addition, this update adds the following Enhancement BZ# 1042996 With this update, support for TLS version 1.2 for mail accounts has been added to Evolution. Users of evolution-data-server are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
9.13. Using SASL with LDAP Clients To use SASL with the LDAP clients, such as ldapsearch , pass the -Y SASL_mechanism to the command. For example: To use the GSSAPI SASL mechanism over the LDAP protocol: To use the PLAIN SASL mechanism over the LDAPS protocol: Note SASL proxy authorization is not supported in Directory Server. Therefore, Directory Server ignores any SASL authzid value supplied by the client.

Commands:
ldapsearch -Y GSSAPI -U "dn:uid= user_name ,ou=people,dc=example,dc=com" -R EXAMPLE.COM -H ldap://server.example.com -b "dc=example,dc=com"
ldapsearch -Y PLAIN -D "uid= user_name ,ou=people,dc=example,dc=com" -W -H ldaps://server.example.com -b "dc=example,dc=com"
Chapter 1. Overview Red Hat OpenShift Data Foundation is software-defined storage that is optimized for container environments. It runs as an operator on OpenShift Container Platform to provide highly integrated and simplified persistent storage management for containers. Red Hat OpenShift Data Foundation is integrated into the latest Red Hat OpenShift Container Platform to address platform services, application portability, and persistence challenges. It provides a highly scalable backend for the generation of cloud-native applications, built on a new technology stack that includes Red Hat Ceph Storage, the Rook.io Operator, and NooBaa's Multicloud Object Gateway technology. Red Hat OpenShift Data Foundation provides a trusted, enterprise-grade application development environment that simplifies and enhances the user experience across the application lifecycle in a number of ways: Provides block storage for databases. Shared file storage for continuous integration, messaging, and data aggregation. Object storage for cloud-first development, archival, backup, and media storage. Scale applications and data exponentially. Attach and detach persistent data volumes at an accelerated rate. Stretch clusters across multiple data-centers or availability zones. Establish a comprehensive application container registry. Support the generation of OpenShift workloads such as Data Analytics, Artificial Intelligence, Machine Learning, Deep Learning, and Internet of Things (IoT). Dynamically provision not only application containers, but data service volumes and containers, as well as additional OpenShift Container Platform nodes, Elastic Block Store (EBS) volumes and other infrastructure services. 1.1. About this release Red Hat OpenShift Data Foundation 4.9 ( RHSA-2021:5085 and RHSA-2021:5086 ) is now available. New enhancements, features, and known issues that pertain to OpenShift Data Foundation 4.9 are included in this topic. Red Hat OpenShift Data Foundation 4.9 is supported on the Red Hat OpenShift Container Platform versions 4.9. For more information, see Red Hat OpenShift Data Foundation Supportability and Interoperability Guide . With the release of OpenShift Data Foundation 4.9, version 4.5 is now end of life. For more information, see Red Hat OpenShift Container Platform Life Cycle Policy .

Commands:
7.164. powerpc-utils 7.164.1. RHBA-2015:1319 - powerpc-utils bug fix and enhancement update Updated powerpc-utils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The powerpc-utils packages provide various utilities for the PowerPC platform. Enhancement BZ# 11248741 It is no longer possible for the "drmgr" command to erroneously remove the last CPU. * Support for up to eight threads in simultaneous multithreading (SMT) has been added. * It is possible to convert an Open Firmware (OF) device path to a logical device path for a virtio SCSI device. * The "snap" command now also warns about possible clear-text password disclosure. Users of powerpc-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 5. Command Line Tools This section describes the behavioral changes of command-line tools in Red Hat Enterprise Linux 6. 5.1. Grep The behavior of the grep command has changed with regards to searching for upper and lower case strings. Using interval searching in the [a-z] format is dependent on the LC_COLLATE variable. You can set LC_COLLATE=C to preserve old behavior and to achieve proper results when performing interval searching with this method; however, in Red Hat Enterprise Linux 6, the recommended way of interval searching is to use the [[:lower:]],[[:upper:]] format. This change can significantly affect output, so scripts and processes must be reviewed to continue to achieve the correct results.

Commands:
Chapter 12. Uninstalling Directory Server If you no longer need a Directory Server instance, you can uninstall it to reclaim space. 12.1. Uninstalling Directory Server If you no longer require Directory Server running on a server, uninstall the packages as described in this section. Procedure Remove all instances from the replication topology. If your instance is not a member of a replication topology skip this step. Remove all instances from the server. For each instance, enter: # dsctl instance_name remove --do-it Remove the Directory Server packages: # dnf module remove redhat-ds Optional: Disable the dirsrv-12-for-rhel-8-x86_64-rpms repository: # subscription-manager repos --disable=dirsrv-12-for-rhel-8-x86_64-rpms Repository 'dirsrv-12-for-rhel-8-x86_64-rpms' is disabled for this system. Optional: Remove the Red Hat Directory Server subscription from the system: Important If you remove a subscription that provides additional products than Directory Server, you will not be able to install or update packages for these products. List the subscriptions attached to the host: # subscription-manager list --consumed Subscription Name: Example Subscription ... Pool-ID: 5ab6a8df96b03fd30aba9a9c58da57a1 ... Remove the subscription using the pool id from the step: # subscription-manager remove --pool= 5ab6a8df96b03fd30aba9a9c58da57a1 2 local certificates have been deleted. The entitlement server successfully removed these pools: 5ab6a8df96b03fd30aba9a9c58da57a1 The entitlement server successfully removed these serial numbers: 1658239469356282126 Additional resources Removing an instance from a replication topology

Commands:
dsctl instance_name remove --do-it
dnf module remove redhat-ds
subscription-manager repos --disable=dirsrv-12-for-rhel-8-x86_64-rpms Repository 'dirsrv-12-for-rhel-8-x86_64-rpms' is disabled for this system.
subscription-manager list --consumed Subscription Name: Example Subscription Pool-ID: 5ab6a8df96b03fd30aba9a9c58da57a1
subscription-manager remove --pool= 5ab6a8df96b03fd30aba9a9c58da57a1 2 local certificates have been deleted. The entitlement server successfully removed these pools: 5ab6a8df96b03fd30aba9a9c58da57a1 The entitlement server successfully removed these serial numbers: 1658239469356282126
1.5. Red Hat JBoss Data Grid Version Information Red Hat JBoss Data Grid is based on Infinispan, the open source community version of the data grid software. Infinispan uses code, designs, and ideas from JBoss Cache, which have been tried, tested, and proved in high stress environments. As a result, JBoss Data Grid's first release is version 6.0 as a result of its deployment history. The following table lists the correlation between JBoss Data Grid and Infinispan versions. Table 1.1. JBoss Data Grid and Infinispan Correlation JBoss Data Grid Product Infinispan Version JBoss Data Grid 6.0.0 Infinispan 5.1.5 JBoss Data Grid 6.0.1 Infinispan 5.1.7 JBoss Data Grid 6.1.0 Infinispan 5.2.4 JBoss Data Grid 6.2.0 Infinispan 6.0.1 JBoss Data Grid 6.3.0 Infinispan 6.1.0 JBoss Data Grid 6.3.1 Infinispan 6.1.1 JBoss Data Grid 6.4.0 Infinispan 6.2.0 JBoss Data Grid 6.4.1 Infinispan 6.2.1 JBoss Data Grid 6.5.0 Infinispan 6.3.0 JBoss Data Grid 6.5.1 Infinispan 6.3.1 JBoss Data Grid 6.6.0 Infinispan 6.4.0 JBoss Data Grid 6.6.1 Infinispan 6.4.1 Note From Red Hat JBoss Data Grid 6.2.0 onwards, there is no direct corresponding version of Infinispan for each JBoss Data Grid release. The Infinispan version provided for JBoss Data Grid 6.3.0 and later are based on an internal version number (possibly an unreleased version) of Infinispan. Report a bug

Commands:
Chapter 2. Red Hat Certification Self Check 2.1. Red Hat certification self check (rhcert/selfcheck) test The Red Hat certification self check test also known as rhcert/selfcheck confirms that all the software packages required in the certification process are installed and that they have not been altered. This ensures that the test environment is ready for the certification process and that all the certification software packages are supportable. Note The certification packages must not be modified for certification testing or for any other purpose. Success criteria The test environment includes all the packages required in the certification process and the packages have not been modified. 2.2. System report The system report (sosreport) test, also known as cloud/sosreport , captures the basic sosreport. Red Hat uses a tool called sos to collect the configuration and diagnostic information from a RHEL system, and to assist customers in troubleshooting their system and following recommended practices. The system report subtest ensures that the sos tool functions as expected on the image/system and captures a basic sosreport. Success criteria A basic sosreport can be captured on the image. Additional resources For more information about sos reports, see What is an sosreport and how to create one in Red Hat Enterprise Linux?

Commands: