mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 22. General Updates Shortening of long network device names Some network devices have unacceptably long names. This is due to certain firmware reporting meaningless data, such as the device's onboard index value, which the kernel passes to user-space. Previously, this resulted in problems with maximum name length, especially with VLANs. With this update, systemd rejects unacceptably long names and falls back to a different naming scheme. As a result, long network device names will no longer appear. IMPORTANT: This also means that names on existing installations might change, and the affected network devices will not go online. The change in name will happen on network cards with names enoX where X is more than 16383. This will mostly affect vmware machines, because their firmware has the described problem. (BZ#1230210) A fix for systemd to read the device identification bytes correctly Due to an endianness problem, the version of systemd in Red Hat Enterprise Linux 7.2 read the device identification bytes in a wrong order, causing the dev/disk/by-id/wwn-* symbolic links to be generated incorrectly. A patch has been applied to put the device identification bytes in the correct order and the symbolic links are now generated correctly. Any reference that depends on the value obtained from /dev/disk/by-id/wwn-* needs to be modified to work correctly in Red Hat Enterprise Linux 7.3 and later. (BZ# 1308795 ) The value of net.unix.max_dgram_qlen increased to 512 Previously, the default value of the net.unix.max_dgram_qlen kernel option was 16. As a consequence, when the network traffic was too high, certain services could terminate unexpectedly. This update sets the value to 512, thus preventing this problem. Users need to reboot the machine to apply this change. (BZ# 1267707 ) Links to non-root file systems in /lib/ and /lib64/ are removed by ldconfig.service Red Hat Enterprise Linux 7.2 introduced ldconfig.service , which is run at an early stage of the boot process, before non-root file systems are mounted. Before this update, when ldconfig.service was run, links in the /lib/ and /lib64/ directories were removed if they pointed to file systems which were not yet mounted. In Red Hat Enterprise Linux 7.3, ldconfig.service has been removed, and the problem no longer occurs. (BZ#1301990) systemd no longer hangs when many processes terminate in a short interval Previously, an inefficient algorithm for reaping processes caused the systemd service to become unresponsive when a large number of processes terminated in a short interval. With this update, the algorithm has been improved, and systemd is now able to reap the processes more quickly, which prevents the described systemd hang from occurring. (BZ#1360160) gnome-dictionary multilib packages conflicts no longer occur When both the 32-bit and 64-bit packages of the gnome-dictionary multilib packages were installed, upgrading from Red Hat Enterprise Linux 7.2 to Red Hat Enterprise Linux 7.3 failed. To fix this problem, the 32-bit package has been removed from Red Hat Enterprise Linux 7.3. As a result, upgrading in this situation works as expected. (BZ#1360338)

Commands:
Chapter 16. complete This chapter describes the commands under the complete command. 16.1. complete print bash completion command Usage: Table 16.1. Command arguments Value Summary -h, --help Show this help message and exit --name <command_name> Command name to support with command completion --shell <shell> Shell being used. use none for data only (default: bash)

Commands:
openstack complete [-h] [--name <command_name>] [--shell <shell>]
Chapter 3. Setting up to Develop Applications Using C and C++ Red Hat Enterprise Linux best supports development using the fully compiled C and C++ programming languages. Select the Development Tools and Debugging Tools Add-ons during the system installation to install the GNU Compiler Collection (GCC) and GNU Debugger (GDB) as well as other development tools. Latest versions of GCC , GDB , and the associated tools are available as a part of the Red Hat Developer Toolset toolchain component. NOTE: Red Hat Developer Toolset is shipped as a Software Collection. The scl utility allows you to use it, running commands with the Red Hat Developer Toolset binaries used in preference to the Red Hat Enterprise Linux system equivalent. The Red Hat Enterprise Linux repositories contain many libraries widely used for the development of C and C++ applications. Install the development packages of the libraries needed for your application using the yum package manager. For graphical-based development, install the Eclipse integrated development environment. The C and C++ languages are directly supported. Eclipse is available as part of Red Hat Developer Tools. For the actual installation procedure, see Using Eclipse . Additional Resources Red Hat Developer Toolset User Guide - Chapter 1., Red Hat Developer Toolset Components

Commands:
yum install devtoolset-9-toolchain
7.44. dropwatch 7.44.1. RHBA-2012:1182 - dropwatch bug fix update Updated dropwatch packages that fix one bug are now available for Red Hat Enterprise Linux 6. The dropwatch package contains a utility that provides packet monitoring services. Bug Fix BZ#725464 Prior to this update, the dropwatch utility could become unresponsive because it was waiting for a deactivation acknowledgement to be issued by an already deactivated or stopped service. With this update, dropwatch detects an attempt to deactivate/stop an already deactivated/stopped service and no longer hangs. All users of dropwatch are advised to upgrade to these updated packages, which fix this bug.

Commands:
Preface Red Hat OpenStack Platform provides the foundation to build a private or public Infrastructure-as-a-Service (IaaS) cloud on top of Red Hat Enterprise Linux. It offers a massively scalable, fault-tolerant platform for the development of cloud-enabled workloads. Network Functions Virtualization (NFV) uses virtualization to move network node functions into building blocks that interconnect to create communication services. NFV is a new way to define, create, and manage networks by replacing dedicated hardware appliances with software and automation. This guide briefly discusses Red Hat's effort to accelerate NFV deployments using the Red Hat OpenStack Platform.

Commands:
Chapter 50. Using the standalone content manager perspective By using the standalone content manager perspective in your application, you can create and edit your application's content and its navigation menus. Procedure Log in to Business Central. In a web browser, enter the following web address in the address bar, http://localhost:8080/business-central/kie-wb.jsp?standalone=true&perspective=ContentManagerPerspective The standalone content manager perspective opens in the browser.

Commands:
8.216. system-config-users-docs 8.216.1. RHBA-2013:1002 - system-config-users-docs bug fix update An updated system-config-users-docs package that fixes one bug is now available for Red Hat Enterprise Linux 6. The system-config-users-docs package contains the online documentation for system-config-users, which is a graphical utility for administrating users and groups. Bug Fix BZ#635248 Previously, text in screenshots was not translated and the untranslated screenshots did not match the running program. This update brings the screenshots up to date and their translations are now included. Users of system-config-users-docs are advised to upgrade to this updated package, which fixes this bug.

Commands:
18.8. Managing ACIs Using the Web Console This set of instructions provides you with the basics of managing the access control instructions (ACIs) by using the LDAP browser wizard in the web console. 18.8.1. Creating an Access Control Instruction in the LDAP browser You can create and add an access control instruction (ACI) for a Red Hat Directory Server (RHDS) entry by using the LDAP Browser in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP Browser . Select an LDAP entry and click the Options menu. From the drop-down menu, select ACIs . To create an ACI by using the LDAP browser wizard, you have two options: Click Add ACI Wizard to create the ACI using the wizard. Continue with the step. Click Add ACI Manually , specify the instruction in the text field, and click Save ACI . Follow the steps in the wizard and click the button after you complete each step. To create the ACI, review the data that the wizard generated, and click Add ACI . To close the wizard window, click the Finish button. Verification Verify the new ACI appears in the Manage ACIs window. 18.8.2. Editing Access Control Instructions in the LDAP browser You can edit an access control instruction (ACI) for a Red Hat Directory Server entry by using the LDAP Browser Manage ACIs window in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP Browser . Select an LDAP entry and click the Options menu. From the drop-down menu, select ACIs . Click the Options menu and select Edit ACI . Modify the instruction in the text field and click Save ACI . Verification On the Manage ACIs window, expand the ACI you modified and observe your changes. 18.8.3. Removing an Access Control Instruction in the LDAP browser You can remove an access control instruction (ACI) for a Red Hat Directory Server entry by using the LDAP Browser in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP Browser . Select an LDAP entry and click the Options menu. From the drop-down menu, select ACIs to open the Manage ACIs window. Click the Node options icon for the ACI you are removing and select Remove ACI . Select the Yes, I'm sure checkbox and click the Delete ACI button. Verification On the Manage ACIs window, verify the ACI you removed no longer appears on the list of ACIs.

Commands:
Chapter 13. Real-Time Kernel About Red Hat Enterprise Linux for Real Time Kernel The Red Hat Enterprise Linux for Real Time Kernel is designed to enable fine-tuning for systems with extremely high determinism requirements. The major increase in the consistency of results can, and should, be achieved by tuning the standard kernel. The real-time kernel enables gaining a small increase on top of increase achieved by tuning the standard kernel. The real-time kernel is available in the rhel-7-server-rt-rpms repository. The Installation Guide contains the installation instructions and the rest of the documentation is available at Product Documentation for Red Hat Enterprise Linux for Real Time . kernel-rt rebased The kernel-rt sources have been upgraded to be based on the latest Red Hat Enterprise Linux kernel source tree, which provides a number of bug fixes and enhancements over the version. (BZ#1391779)

Commands:
7.2. Moving Resources Due to Failure When you create a resource, you can configure the resource so that it will move to a new node after a defined number of failures by setting the migration-threshold option for that resource. Once the threshold has been reached, this node will no longer be allowed to run the failed resource until: The administrator manually resets the resource's failcount using the pcs resource failcount command. The resource's failure-timeout value is reached. There is no threshold defined by default. Note Setting a migration-threshold for a resource is not the same as configuring a resource for migration, in which the resource moves to another location without loss of state. The following example adds a migration threshold of 10 to the resource named dummy_resource , which indicates that the resource will move to a new node after 10 failures. You can add a migration threshold to the defaults for the whole cluster with the following command. To determine the resource's current failure status and limits, use the pcs resource failcount command. There are two exceptions to the migration threshold concept; they occur when a resource either fails to start or fails to stop. If the cluster property start-failure-is-fatal is set to true (which is the default), start failures cause the failcount to be set to INFINITY and thus always cause the resource to move immediately. Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout.

Commands:
pcs resource meta dummy_resource migration-threshold=10
pcs resource defaults migration-threshold=10
Chapter 6. Creating alerts in Datadog Administrators can create monitors that track the metrics of the Red Hat Ceph Storage cluster and generate alerts. For example, if an OSD is down, Datadog can alert an administrator that one or more OSDs are down. Prerequisites Root-level access to the Ceph Monitor node. Appropriate Ceph key providing access to the Red Hat Ceph Storage cluster. Internet access. Procedure Click Monitors to see an overview of the Datadog monitors. To create a monitor, select Monitors->New Monitor . Select the detection method. For example, "Threshold Alert." Define the metric. To create an advanced alert, click on the Advanced... link. Then, select a metric from the combo box. For example, select the ceph.num_in_osds Ceph metric. Click Add Query+ to add another query. Select another metric from the combo box. For example, select the ceph.num_up_osds Ceph metric. In the Express these queries as: field, enter a-b , where a is the value of ceph.num_in_osds and b is the value of ceph.num_up_osds . When the difference is 1 or greater, there is at least one OSD down. Set the alert conditions. For example, set the trigger to be above or equal to , the threshold to in total and the time elapsed to 1 minute . Set the Alert threshold field to 1 . When at least one OSD is in the cluster and it is not up and running, the monitor will alert the user. Give the monitor a title in the input field below Preview and Edit . This is required to save the monitor. Enter a description of the alert in the text field. Note The text field supports metric variables and Markdown syntax. Add the recipients of the alert. This will add an email address to the text field. When the alert gets triggered, the recipients will receive the alert.

Commands:
Chapter 19. Troubleshooting issues in provider mode 19.1. Force deletion of storage in provider clusters When a client cluster is deleted without performing the offboarding process to remove all the resources from the corresponding provider cluster, you need to perform force deletion of the corresponding storage consumer from the provider cluster. This helps to release the storage space that was claimed by the client. Caution It is recommended to use this method only in unavoidable situations such as accidental deletion of storage client clusters. Prerequisites Access to the OpenShift Data Foundation storage cluster in provider mode. Procedure Click Storage Storage Clients from the OpenShift console. Click the delete icon at the far right of the listed storage client cluster. The delete icon is enabled only after 5 minutes of the last heartbeat of the cluster. Click Confirm .

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 9.2 is distributed with the kernel version 5.14.0-284.11.1, which provides support for the following architectures at the minimum required version: AMD and Intel 64-bit architectures (x86-64-v2) The 64-bit ARM architecture (ARMv8.0-A) IBM Power Systems, Little Endian (POWER9) 64-bit IBM Z (z14) Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures .

Commands:
4.31. coolkey 4.31.1. RHEA-2011:1738 - coolkey enhancement update An enhanced coolkey package is now available for Red Hat Enterprise Linux 6. The coolkey package contains driver support for CoolKey and Common Access Card (CAC) smart card products. Enhancements BZ# 578690 This update adds support for Personal Identity Verification (PIV) smart cards. BZ# 700907 Common Access Cards (CAC) are defined to have exactly three certificates. However, some cards that used the CAC interface supplied one or two certificates only, which may have caused the coolkey utility to fail. CAC smart cards that contain less than three certificates are now supported. Users of PIV and CAC smart cards are advised to upgrade to this updated package, which adds these enhancements.

Commands:
5.357. wpa_supplicant 5.357.1. RHBA-2013:0225 - wpa_supplicant bug fix and enhancement update Updated wpa_supplicant packages that fix one bug and add an enhancement are now available for Red Hat Enterprise Linux 6. The wpa_supplicant packages contain an 802.1X Supplicant with support for WEP, WPA, WPA2 (IEEE 802.11i / RSN), and various EAP authentication methods. It implements key negotiation with a WPA Authenticator for client stations and controls the roaming and IEEE 802.11 authentication/association of the WLAN driver. Bug Fix BZ# 855255 Previously, the supplicant would attempt to roam to slightly stronger access points, increasing the chance of a disconnection. This bug has been fixed and the supplicant now only attempts to roam to a stronger access point when the current signal is significantly degraded. Enhancement BZ# 855273 Support for Opportunistic Key Caching (OKC), also known as Proactive Key Caching (PKC), has been added to WPA Supplicant to facilitate faster and less error-prone roaming between access points in the same network. Users of wpa_supplicant are advised to upgrade to these updated packages, which fix this bug and add this enhancement. 5.357.2. RHBA-2012:0978 - wpa_supplicant bug fix update An updated wpa_supplicant package that fixes a bug is now available for Red Hat Enterprise Linux 6. The wpa_supplicant package contains a WPA (Wi-Fi Protected Access) Supplicant utility for Linux, BSD, and Windows with support for WPA and WPA2 (IEEE 802.11i/RSN). The supplicant is an IEEE 802.1X/WPA component that is used in client workstations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication and association of the WLAN driver. Bug Fix BZ# 752032 Due to an error in the wpa_supplicant code, Wi-Fi signal levels for some wireless devices reported by the Linux kernel's nl80211 API were not handled correctly. Consequently, the NetworkManager applet did not indicate the signal strength for unconnected networks. With this update, the code has been corrected and the NetworkManager applet now indicates signal strength for drivers using the nl80211 API as expected. All users of wpa_supplicant are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. OpenShift Container Platform CI/CD overview OpenShift Container Platform is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the OpenShift Container Platform provides the following CI/CD solutions: OpenShift Builds OpenShift Pipelines OpenShift GitOps 1.1. OpenShift Builds With OpenShift Builds, you can create cloud-native apps by using a declarative build process. You can define the build process in a YAML file that you use to create a BuildConfig object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the BuildConfig object typically builds a runnable image and pushes it to a container image registry. OpenShift Builds provides the following extensible support for build strategies: Docker build Source-to-image (S2I) build Custom build For more information, see Understanding image builds 1.2. OpenShift Pipelines OpenShift Pipelines provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes. For more information, see Understanding OpenShift Pipelines 1.3. OpenShift GitOps OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. For more information, see Understanding OpenShift GitOps 1.4. Jenkins Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the OpenShift Container Platform. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart.

Commands:
Chapter 1. Using Ansible plug-ins for Red Hat Developer Hub Ansible plug-ins for Red Hat Developer Hub deliver an Ansible-specific portal experience with curated learning paths, push-button content creation, integrated development tools, and other opinionated resources. Important The Ansible plug-ins are a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. To use the Ansible plugins, see Using Ansible plug-ins for Red Hat Developer Hub .

Commands:
7.106. libpcap 7.106.1. RHBA-2015:1288 - libpcap bug fix update Updated libpcap packages that fix one bug are now available for Red Hat Enterprise Linux 6. Libpcap provides a portable framework for low-level network monitoring. Libpcap can provide network statistics collection, security monitoring and network debugging. Bug Fix BZ# 1025841 , BZ# 1063328 Previously, running the "tcpdump" command with the filter expression containing the keyword "vlan" produced unexpected output, as the filter generated by the libpcap Berkeley Packet Filter (BPF) compiler did not employ BPF extensions. To fix this bug, libpcap has been amended and now generates filters that use BPF extensions when appropriate. As a result, running "tcpdump" with filters containing "vlan" produces correct results. Users of libpcap are advised to upgrade to these updated packages, which fix this bug.

Commands: