mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 9. Asynchronous errata updates 9.1. RHSA-2025:0323 OpenShift Data Foundation 4.14.13 bug fixes and security updates OpenShift Data Foundation release 4.14.13 is now available. The bug fixes that are included in the update are listed in the RHSA-2025:0323 advisory. 9.2. RHBA-2024:10129 OpenShift Data Foundation 4.14.12 bug fixes and security updates OpenShift Data Foundation release 4.14.12 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:10129 advisory. 9.3. RHSA-2024:7624 OpenShift Data Foundation 4.14.11 bug fixes and security updates OpenShift Data Foundation release 4.14.11 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:7624 advisory. 9.4. RHBA-2024:6398 OpenShift Data Foundation 4.14.10 bug fixes and security updates OpenShift Data Foundation release 4.14.10 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:6398 advisory. 9.5. RHBA-2024:4217 OpenShift Data Foundation 4.14.9 bug fixes and security updates OpenShift Data Foundation release 4.14.9 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:4217 advisory. 9.6. RHBA-2024:3861 OpenShift Data Foundation 4.14.8 bug fixes and security updates OpenShift Data Foundation release 4.14.8 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:3861 advisory. 9.7. RHBA-2024:3443 OpenShift Data Foundation 4.14.7 bug fixes and security updates OpenShift Data Foundation release 4.14.7 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:3443 advisory. 9.8. RHBA-2024:1579 OpenShift Data Foundation 4.14.6 bug fixes and security updates OpenShift Data Foundation release 4.14.6 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:1579 advisory. 9.9. RHBA-2024:1043 OpenShift Data Foundation 4.14.5 bug fixes and security updates OpenShift Data Foundation release 4.14.5 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:1043 advisory. 9.10. RHBA-2024:0315 OpenShift Data Foundation 4.14.4 bug fixes and security updates OpenShift Data Foundation release 4.14.4 is now available. The bug fixes that are included in the update are listed in the RHBA-2024:0315 advisory. 9.11. RHBA-2023:7869 OpenShift Data Foundation 4.14.3 bug fixes and security updates OpenShift Data Foundation release 4.14.3 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:7869 advisory. 9.12. RHBA-2023:7776 OpenShift Data Foundation 4.14.2 bug fixes and security updates OpenShift Data Foundation release 4.14.2 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:7776 advisory. 9.13. RHBA-2023:7696 OpenShift Data Foundation 4.14.1 bug fixes and security updates OpenShift Data Foundation release 4.14.1 is now available. The bug fixes that are included in the update are listed in the RHBA-2023:7696 advisory.

Commands:
Chapter 108. Verifying permissions of IdM configuration files using Healthcheck Learn more about how to test Identity Management (IdM) configuration files using the Healthcheck tool. For details, see Healthcheck in IdM . Prerequisites The Healthcheck tool is only available on RHEL 8.1 or newer systems. 108.1. File permissions Healthcheck tests The Healthcheck tool tests ownership and permissions of some important files installed or configured by Identity Management (IdM). If you change the ownership or permissions of any tested file, the test returns a warning in the result section. While it does not necessarily mean that the configuration will not work, it means that the file differs from the default configuration. To see all tests, run the ipa-healthcheck with the --list-sources option: You can find the file permissions test under the ipahealthcheck.ipa.files source: IPAFileNSSDBCheck This test checks the 389-ds NSS database and the Certificate Authority (CA) database. The 389-ds database is located in /etc/dirsrv/slapd-<dashed-REALM> and the CA database is located in /etc/pki/pki-tomcat/alias/ . IPAFileCheck This test checks the following files: /var/lib/ipa/ra-agent.{key|pem} /var/lib/ipa/certs/httpd.pem /var/lib/ipa/private/httpd.key /etc/httpd/alias/ipasession.key /etc/dirsrv/ds.keytab /etc/ipa/ca.crt /etc/ipa/custodia/server.keys If PKINIT is enabled: /var/lib/ipa/certs/kdc.pem /var/lib/ipa/private/kdc.key If DNS is configured: /etc/named.keytab /etc/ipa/dnssec/ipa-dnskeysyncd.keytab TomcatFileCheck This test checks some tomcat-specific files if a CA is configured: /etc/pki/pki-tomcat/password.conf /var/lib/pki/pki-tomcat/conf/ca/CS.cfg /etc/pki/pki-tomcat/server.xml Note Run these tests on all IdM servers when trying to find issues. 108.2. Screening configuration files using Healthcheck Follow this procedure to run a standalone manual test of an Identity Management (IdM) server's configuration files using the Healthcheck tool. The Healthcheck tool includes many tests. Results can be narrowed down by: Excluding all successful test: --failures-only Including only ownership and permissions tests: --source=ipahealthcheck.ipa.files Procedure To run Healthcheck tests on IdM configuration file ownership and permissions, while displaying only warnings, errors and critical issues, enter: A successful test displays empty brackets: Failed tests display results similar to the following WARNING : Additional resources See man ipa-healthcheck .

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source=ipahealthcheck.ipa.files --failures-only
ipa-healthcheck --source=ipahealthcheck.ipa.files --failures-only []
{ "source": "ipahealthcheck.ipa.files", "check": "IPAFileNSSDBCheck", "result": "WARNING", "kw": { "key": "_etc_dirsrv_slapd-EXAMPLE-TEST_pkcs11.txt_mode", "path": "/etc/dirsrv/slapd-EXAMPLE-TEST/pkcs11.txt", "type": "mode", "expected": "0640", "got": "0666", "msg": "Permissions of /etc/dirsrv/slapd-EXAMPLE-TEST/pkcs11.txt are 0666 and should be 0640" } }
7.131. lm_sensors 7.131.1. RHBA-2012:1309 - lm_sensors bug fixes Updated lm_sensors packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The lm_sensors packages provide a set of modules for general SMBus access and hardware monitoring. Bug Fixes BZ# 610000 , BZ#623587 Prior to this update, the sensors-detect script did not detect all GenuineIntel CPUs. As a consequence, lm_sensors did not load coretemp module automatically. This update uses a more generic detection for Intel CPUs. Now, the coretemp module is loaded as expected. BZ#768365 Prior to this update, the sensors-detect script reported an error when running without user-defined input. This behavior had no impact on the function but could confuse users. This update modifies the underlying code to allow for the sensors-detect script to run without user. All users of lm_sensors are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. Verifying the Metrics Store installation Verify the Metrics Store installation using the Kibana console. You can view the collected logs and create data visualizations. Procedure Log in to the Kibana console using the URL ( https://kibana. example.com ) that you recorded in Section 2.3, "Deploying Metrics Store services on Red Hat OpenShift" . Use the default admin user, and the password you defined during the metrics store installation. Optionally, you can access the Red Hat OpenShift Container Platform portal at https:// example.com :8443 (using the same admin user credentials). Select the Discover tab, and check that you can view the project.ovirt-logs- ovirt_env_name-uuid index. See the Discover section in the Kibana User Guide for information about working with logs. Select the Visualize tab, where you can create data visualizations for the project.ovirt-metrics- ovirt_env_name-uuid and the project.ovirt-logs- ovirt_env_name-uuid indexes. The Metrics Store User Guide describes the available parameters. See the Visualize section of the Kibana User Guide for information about visualizing logs and metrics.

Commands:
Chapter 8. Setting up the test environment for non-containerized application testing The first step towards certifying your product is setting up the environment where you can run the tests. The test environment consists of a system in which all the certification tests are run. 8.1. Setting up a system that acts as a system under test A system on which the product that needs certification is installed or configured is referred to as the system under test (SUT). Prerequisites The SUT has RHEL version 8 or 9 installed. For convenience, Red Hat provides kickstart files to install the SUT's operating system. Follow the instructions in the file that is appropriate for your system before launching the installation process. Procedure Configure the Red Hat Certification repository: Use your RHN credentials to register your system using Red Hat Subscription Management: Display the list of available subscriptions for your system: Search for the subscription which provides the Red Hat Certification (for RHEL Server) repository and make a note of the subscription and its Pool ID. Attach the subscription to your system: Replace the pool_ID with the Pool ID of the subscription. Note You don't have to attach the subscription to your system, if you enable the option Simple content access for Red Hat Subscription Management . For more details, see How do I enable Simple Content Access for Red Hat Subscription Management? Subscribe to the Red Hat Certification channel: On RHEL 8: Replace HOSTTYPE with the system architecture. To find out the system architecture, run Example: On RHEL 9: Replace HOSTTYPE with the system architecture. To find out the system architecture, run Example: Install the software test suite package:

Commands:
subscription-manager register
subscription-manager list --available*
subscription-manager attach --pool= <pool_ID >
subscription-manager repos --enable=cert-1-for-rhel-8- <HOSTTYPE> -rpms
uname -m
subscription-manager repos --enable=cert-1-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=cert-1-for-rhel-9- <HOSTTYPE> -rpms
uname -m
subscription-manager repos --enable=cert-1-for-rhel-9-x86_64-rpms
dnf install redhat-certification-software
Chapter 1. Introduction to Automation execution environments Using Ansible content that depends on non-default dependencies can be complicated because the packages must be installed on each node, interact with other software installed on the host system, and be kept in sync. Automation execution environments help simplify this process and can easily be created with Ansible Builder. 1.1. About automation execution environments All automation in Red Hat Ansible Automation Platform runs on container images called automation execution environments. Automation execution environments create a common language for communicating automation dependencies, and offer a standard way to build and distribute the automation environment. An automation execution environment should contain the following: Ansible Core 2.16 or later Python 3.10 or later Ansible Runner Ansible content collections and their dependencies System dependencies 1.1.1. Why use automation execution environments? With automation execution environments, Red Hat Ansible Automation Platform has transitioned to a distributed architecture by separating the control plane from the execution plane. Keeping automation execution independent of the control plane results in faster development cycles and improves scalability, reliability, and portability across environments. Red Hat Ansible Automation Platform also includes access to Ansible content tools, making it easy to build and manage automation execution environments. In addition to speed, portability, and flexibility, automation execution environments provide the following benefits: They ensure that automation runs consistently across multiple platforms and make it possible to incorporate system-level dependencies and collection-based content. They give Red Hat Ansible Automation Platform administrators the ability to provide and manage automation environments to meet the needs of different teams. They allow automation to be easily scaled and shared between teams by providing a standard way of building and distributing the automation environment. They enable automation teams to define, build, and update their automation environments themselves. Automation execution environments provide a common language to communicate automation dependencies.

Commands:
Chapter 2. Red Hat Process Automation Manager components The product is made up of Business Central and KIE Server. Business Central is the graphical user interface where you create and manage business rules. You can install Business Central in a Red Hat JBoss EAP instance or on the Red Hat OpenShift Container Platform (OpenShift). Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server. KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. You can install KIE Server in a Red Hat JBoss EAP instance, in a Red Hat JBoss EAP cluster, on OpenShift, in an Oracle WebLogic server instance, in an IBM WebSphere Application Server instance, or as a part of Spring Boot application. You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). A KIE container is a specific version of a project. If KIE Server is managed, the Process Automation Manager controller manages the KIE Server configuration and you interact with the Process Automation Manager controller to create and maintain KIE containers. The Process Automation Manager controller is integrated with Business Central. If you install Business Central on Red Hat JBoss EAP, use the Execution Server page to create and maintain KIE containers. However, if you do not install Business Central, you can install the headless Process Automation Manager controller and use the REST API or the KIE Server Java Client API to interact with it. Red Hat build of OptaPlanner is integrated in Business Central and KIE Server. It is a lightweight, embeddable planning engine that optimizes planning problems. Red Hat build of OptaPlanner helps Java programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with efficient score calculations.

Commands:
Chapter 19. console This chapter describes the commands under the console command. 19.1. console log show Show server's console output Usage: Table 19.1. Positional arguments Value Summary <server> Server to show console log (name or id) Table 19.2. Command arguments Value Summary -h, --help Show this help message and exit --lines <num-lines> Number of lines to display from the end of the log (default=all) 19.2. console url show Show server's remote console URL Usage: Table 19.3. Positional arguments Value Summary <server> Server to show url (name or id) Table 19.4. Command arguments Value Summary -h, --help Show this help message and exit --novnc Show novnc console url (default) --xvpvnc Show xvpvnc console url --spice Show spice console url --rdp Show rdp console url --serial Show serial console url --mks Show webmks console url Table 19.5. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 19.6. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 19.7. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 19.8. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack console log show [-h] [--lines <num-lines>] <server>
openstack console url show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] [--novnc | --xvpvnc | --spice | --rdp | --serial | --mks] <server>
E.2.2. /proc/cmdline This file shows the parameters passed to the kernel at the time it is started. A sample /proc/cmdline file looks like the following: This tells us that the kernel is mounted read-only (signified by (ro) ), located on the first logical volume ( LogVol00 ) of the first volume group ( /dev/VolGroup00 ). LogVol00 is the equivalent of a disk partition in a non-LVM system (Logical Volume Management), just as /dev/VolGroup00 is similar in concept to /dev/hda1 , but much more extensible. For more information on LVM used in Red Hat Enterprise Linux, see http://www.tldp.org/HOWTO/LVM-HOWTO/index.html . , rhgb signals that the rhgb package has been installed, and graphical booting is supported, assuming /etc/inittab shows a default runlevel set to id:5:initdefault: . Finally, quiet indicates all verbose kernel messages are suppressed at boot time.

Commands:
ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
Chapter 7. Enabling Chinese, Japanese, or Korean text input If you write with Chinese, Japanese, or Korean characters, you can configure RHEL to input text in your language. 7.1. Input methods Certain scripts, such as Chinese, Japanese, or Korean, require keyboard input to go through an Input Method Engine (IME) to enter native text. An input method is a set of conversion rules between the text input and the selected script. An IME is a software that performs the input conversion specified by the input method. To input text in these scripts, you must set up an IME. If you installed the system in your native language and selected your language at the GNOME Initial Setup screen, the input method for your language is enabled by default. 7.2. Available input method engines The following input method engines (IMEs) are available on RHEL from the listed packages: Table 7.1. Available input method engines Languages Scripts IME name Package Chinese Simplified Chinese Intelligent Pinyin ibus-libpinyin Chinese Traditional Chinese New Zhuyin ibus-libzhuyin Japanese Kanji, Hiragana, Katakana Anthy ibus-anthy Korean Hangul Hangul ibus-hangul Other Various M17N ibus-m17n 7.3. Installing input method engines This procedure installs input method engines (IMEs) that you can use to input Chinese, Japanese, and Korean text. Procedure Install all available input method packages: 7.4. Switching the input method in GNOME This procedure sets up the input method for your script, such as for Chinese, Japanese, or Korean scripts. Prerequisites The input method packages are installed. Procedure Go to the system menu , which is accessible from the top-right screen corner, and click Settings . Select the Keyboard section. In the Input Sources list, review the currently enabled input methods. If your input method is missing: Click the + button under the Input Sources list. Select your language. Note If you cannot find your language in the menu, click the three dots icon ( More... ) at the end of the menu. Select the input method that you want to use. A cog wheel icon marks all input methods to distinguish them from simple keyboard layouts. Confirm your selection by clicking Add . Switch the active input method using one of the following ways: Click the input method indicator on the right side of the top panel and select your input method. Switch between the enabled input methods using the Super + Space keyboard shortcut. Verification Open a text editor. Type text in your language. Verify that the text appears in your native script. 7.5. Additional resources Installing a font for the Chinese standard GB 18030 character set (Red Hat Knowledgebase)

Commands:
dnf install @input-methods
Preface The company SSO integration feature allows you to log in to your Red Hat account by using your company login credentials instead of your Red Hat account credentials. Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message .

Commands:
Preface After installing Red Hat Ansible Automation Platform, your system might need extra configuration to ensure your deployment runs smoothly. This guide provides procedures for configuration tasks that you can perform after installing Red Hat Ansible Automation Platform. Disclaimer : Links contained in this information to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

Commands:
11.2. Time/Date Based Expressions Date expressions are used to control a resource or cluster option based on the current date/time. They can contain an optional date specification. Table 11.4. Properties of a Date Expression Field Description start A date/time conforming to the ISO8601 specification. end A date/time conforming to the ISO8601 specification. operation Compares the current date/time with the start or the end date or both the start and end date, depending on the context. Allowed values: * gt - True if the current date/time is after start * lt - True if the current date/time is before end * in-range - True if the current date/time is after start and before end * date-spec - performs a cron-like comparison to the current date/time

Commands: