mtpti5iD/redhat-docs_dataset huggingface dataset:
15.2.2. Removing an LVM2 Logical Volume for Swap To remove a swap volume group (assuming /dev/VolGroup00/LogVol02 is the swap volume you want to remove): Procedure 15.4. Remove a swap volume group Disable swapping for the associated logical volume: Remove the LVM2 logical volume of size 512 MB: Remove the following entry from the /etc/fstab file: /dev/VolGroup00/LogVol02 swap swap defaults 0 0 To test if the logical volume size was successfully removed, use cat /proc/swaps or free to inspect the swap space.

Commands:
swapoff -v /dev/VolGroup00/LogVol02
lvremove /dev/VolGroup00/LogVol02
8.131. opencv 8.131.1. RHBA-2013:1118 - opencv bug fix update Updated opencv packages that fix one bug are now available for Red Hat Enterprise Linux 6. OpenCV is the open source computer vision library. It is a collection of C functions and C++ classes that implement Image Processing and Computer Vision algorithms. Bug Fix BZ#658060 The OpenCVConfig.cmake file had different contents on 32-bit and 64-bit architecture and was installed under the /usr/share directory. Consequently, the opencv-devel package could not be installed in a multilib environment. With this update, the OpenCVConfig.cmake file has been moved to the /usr/lib(64) directory and the opencv-devel package can now be installed in a multilib environment. Users of opencv are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 10. Uninstalling a cluster on VMC You can remove a cluster installed on VMware vSphere infrastructure that you deployed to VMware Cloud (VMC) on AWS by using installer-provisioned infrastructure. 10.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with User Provisioned Infrastructure (UPI) clusters. There might be resources that the installer did not create or that the installer is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure From the directory that contains the installation program on the computer that you used to install the cluster, run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
Chapter 3. Selecting an installed Red Hat build of OpenJDK version for a specific application Some applications require a specific Red Hat build of OpenJDK version to run. If multiple versions of Red Hat build of OpenJDK are installed on the system using the yum package manager or portable bundle, you can select a Red Hat build of OpenJDK version for each application where necessary by setting the value of the JAVA_HOME environment variable or using a wrapper script. Prerequisites Multiple versions of Red Hat build of OpenJDK installed on the machine. Ensure that the application you want to run is installed. Procedure Set the JAVA_HOME environment variable. For example, if openjdk-8 was installed using yum : USD JAVA_HOME=/usr/lib/jvm/java-8-openjdk Note The symbolic link java-8-openjdk is controlled by the alternatives command. Do one of the following: Launch the application using the default, system-wide configuration. Launch the application specifying the JAVA_HOME variable:

Commands:
mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 1.8.0_242, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el8_1.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-147.3.1.el8_1.x86_64", arch: "amd64", family: "unix"
JAVA_HOME=/usr/lib/jvm/java-8-openjdk mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 1.8.0_242, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk-1.8.0.242.b08-0.el8_1.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.12-200.el8_1.x86_64", arch: "amd64", family: "unix"
Chapter 5. New features for the Red Hat build of OpenJDK 21 The initial release of Red Hat build of OpenJDK 21 includes new features that enhance the use of your Java applications. Red Hat build of OpenJDK 21 includes the following new features: UTF-8 by default For more information, see JEP 400: UTF-8 by Default . Simple web server For more information, see JEP 408: Simple Web Server . Code snippets in Java API documentation For more information, see JEP 413: Code Snippets in Java API Documentation . Reimplement core reflection with method handles For more information, see JEP 416: Reimplement Core Reflection with Method Handles . Internet-address resolution SPI For more information, see JEP 418: Internet-Address Resolution SPI . Linux/RISC-V port For more information, see JEP 422: Linux/RISC-V Port . Scoped values (Preview feature) For more information, see JEP 429: Scoped Values (Preview) . String templates (Preview feature) For more information, see JEP 430: String Templates (Preview) . Sequenced collections For more information, see JEP 431: Sequenced Collections . Generational Z Garbage Collector (ZGC) For more information, see JEP 439: Generational ZGC . Record patterns For more information, see JEP 440: Record Patterns . Pattern matching for switch For more information, see JEP 441: Pattern Matching for switch . Foreign function and memory (FFM) API (Third preview) For more information, see JEP 442: Foreign Function & Memory API (Third Preview) . Unnamed patterns and variables (Preview feature) For more information, see JEP 443: Unnamed Patterns and Variables (Preview) . Virtual threads For more information, see JEP 444: Virtual Threads . Unnamed classes and instance main methods (Preview feature) For more information, see JEP 445: Unnamed Classes and Instance Main Methods (Preview) . Scoped values (preview) For more information, see JEP 446: Scoped Values (Preview) . Vector API (sixth incubator) For more information, see JEP 448: Vector API (Sixth Incubator) . Key encapsulation mechanism API For more information, see JEP 452: Key Encapsulation Mechanism API . Structured concurrency (Preview feature) For more information, see JEP 453: Structured Concurrency (Preview) .

Commands:
9.9. Other Performance Tuning Considerations Although, you can find information about all JBoss Data Services settings using the Management CLI (see Section 10.1, "JBoss Data Virtualization Settings" ), this section provides some additional information about the max-source-rows setting. max-source-rows When using JBoss Data Services in a development environment, you may consider setting max-source-rows to a small value (for example, 10000) to prevent large amounts of data from being pulled from sources. Leaving the exception-on-max-source-rows property set to true will alert the developer through an exception that an attempt was made to retrieve more than the specified number of rows.

Commands:
Chapter 4. Event-Driven Ansible Event-Driven Ansible is a new way to enhance and expand automation by improving IT speed and agility while enabling consistency and resilience. Event-Driven Ansible is designed for simplicity and flexibility. Known issues Both contributor and editor roles cannot set the AWX token. Only users with administrator roles can set the AWX token. Activation-job pods do not have request limits. The onboarding wizard does not request a controller token creation. Users cannot filter through a list of tokens under the Controller Token tab. Only the users with administrator rights can set or change their passwords. If there is a failure, an activation with restart policy set to Always is unable to restart the failed activation. Disabling and enabling an activation causes the restart count to increase by one count. This behavior results in an incorrect restart count. You must run Podman pods with memory limits. Users can add multiple tokens even when only the first AWX token is used. A race condition occurs when creating and rapidly deleting an activation causes errors. When users filter any list, only the items that are on the list get filtered. When ongoing activations start multiple jobs, a few jobs are not recorded in the audit logs. When a job template fails, a few key attributes are missing in the event payload. Restart policy in a Kubernetes deployment does not restart successful activations that are marked as failed. An incorrect status is reported for activations that are disabled or enabled. If the run_job_template action fails, the rule is not counted as executed. RHEL 9.2 activations cannot connect to the host. Restarting the Event-Driven Ansible server can cause activation states to become stale. Bulk deletion of rulebook activation lists is not consistent, and the deletion can be either successful or unsuccessful. When users access the detail screen of a rule audit, the related rulebook activation link is broken. Long running activations with loads of events can cause an out of disk space issue. Resolved in installer release 2.4-6 . Certain characters, such as hyphen (-), forward slash (/), and period (.), are not supported in the event keys. Resolved in installer release 2.4-3 . When there are more activations than available workers, disabling the activations incorrectly shows them in running state. Resolved in installer release 2.4-3 . Event-Driven Ansible activation pods are running out of memory on RHEL 9. Resolved in installer release 2.4-3 . When all workers are busy with activation processes, other asynchronous tasks are not executed, such as importing projects. Resolved in installer release 2.4-3 .

Commands:
Network APIs OpenShift Container Platform 4.17 Reference guide for network APIs Red Hat OpenShift Documentation Team

Commands:
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
{ Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }
a: [ 10.10.1.1:8675, 10.10.2.2:8675 ], b: [ 10.10.1.1:309, 10.10.2.2:309 ]
Chapter 8. Uninstalling the Migration Toolkit for Virtualization You can uninstall the Migration Toolkit for Virtualization (MTV) by using the Red Hat OpenShift web console or the command line interface (CLI). 8.1. Uninstalling MTV by using the Red Hat OpenShift web console You can uninstall Migration Toolkit for Virtualization (MTV) by using the Red Hat OpenShift web console to delete the openshift-mtv project and custom resource definitions (CRDs). Prerequisites You must be logged in as a user with cluster-admin privileges. Procedure Click Home Projects . Locate the openshift-mtv project. On the right side of the project, select Delete Project from the Options menu . In the Delete Project pane, enter the project name and click Delete . Click Administration CustomResourceDefinitions . Enter forklift in the Search field to locate the CRDs in the forklift.konveyor.io group. On the right side of each CRD, select Delete CustomResourceDefinition from the Options menu . 8.2. Uninstalling MTV from the command line interface You can uninstall Migration Toolkit for Virtualization (MTV) from the command line interface (CLI) by deleting the openshift-mtv project and the forklift.konveyor.io custom resource definitions (CRDs). Prerequisites You must be logged in as a user with cluster-admin privileges. Procedure Delete the project: USD oc delete project openshift-mtv Delete the CRDs: USD oc get crd -o name | grep 'forklift' | xargs oc delete Delete the OAuthClient: USD oc delete oauthclient/forklift-ui

Commands:
oc delete project openshift-mtv
oc get crd -o name | grep 'forklift' | xargs oc delete
oc delete oauthclient/forklift-ui
18.7.2. Routed Mode This section provides information about routed mode. DMZ Consider a network where one or more nodes are placed in a controlled subnetwork for security reasons. The deployment of a special subnetwork such as this is a common practice, and the subnetwork is known as a DMZ. Refer to the following diagram for more details on this layout: Figure 18.8. Sample DMZ configuration Host physical machines in a DMZ typically provide services to WAN (external) host physical machines as well as LAN (internal) host physical machines. As this requires them to be accessible from multiple locations, and considering that these locations are controlled and operated in different ways based on their security and trust level, routed mode is the best configuration for this environment. Virtual Server Hosting Consider a virtual server hosting company that has several host physical machines, each with two physical network connections. One interface is used for management and accounting, the other is for the virtual machines to connect through. Each guest has its own public IP address, but the host physical machines use private IP address as management of the guests can only be performed by internal administrators. Refer to the following diagram to understand this scenario: Figure 18.9. Virtual server hosting sample configuration

Commands:
Chapter 2. Overview .NET is a general purpose, modular, cross-platform, and open source implementation of .NET that features automatic memory management and modern programming languages. It allows users to build high-quality applications efficiently. .NET is available on RHEL 7, RHEL 8, RHEL 9. .NET 6.0 is a Long Term Support (LTS) release. LTS releases are generally supported for around 3 years. For more information, see the Life Cycle and Support Policies for the .NET Program . .NET offers: The ability to follow a microservices-based approach, where some components are built with .NET and others with Java, but all can run on a common, supported platform in RHEL. The capacity to more easily develop new .NET workloads on Microsoft Windows. You can deploy and run on either RHEL or Windows Server. A heterogeneous data center, where the underlying infrastructure is capable of running .NET applications without having to rely solely on Windows Server.

Commands:
Chapter 31. Adding the IdM CA service to an IdM server in a deployment with a CA If your Identity Management (IdM) environment already has the IdM certificate authority (CA) service installed but a particular IdM server, idmserver , was installed as an IdM replica without a CA, you can add the CA service to idmserver by using the ipa-ca-install command. Note This procedure is identical for both the following scenarios: The IdM CA is a root CA. The IdM CA is subordinate to an external, root CA. Prerequisites You have root permissions on idmserver . The IdM server is installed on idmserver . Your IdM deployment has a CA installed on another IdM server. You know the IdM Directory Manager password. Procedure On idmserver , install the IdM Certificate Server CA:

Commands:
[root@idmserver ~] ipa-ca-install
B.77. python-gudev B.77.1. RHBA-2010:0850 - python-gudev bug fix update An updated python-gudev package that fixes a bug is now available for Red Hat Enterprise Linux 6. Python-gudev is one of the core components for Red Hat Network (RHN) registration process. Bug Fix BZ# 637084 Under some circumstances, using the 'rhn_register' command to register a system with the Red Hat Network (RHN) might fail. When this issue is encountered, the 'rhn_register' command will return an error similar to: or With this update, the aforementioned errors are no longer returned and using the 'rhn_register' command works as expected. All users of python-gudev are advised to upgrade to this updated package, which resolves this issue.

Commands:
rhn_register Segmentation fault (core dumped)
rhn_register ***MEMORY-ERROR***: rhn_register[11525]: GSlice: assertion failed: sinfo->n_allocated > 0 Aborted (core dumped)
Appendix A. Using an NFS Share for Content Storage Your environment requires adequate hard disk space to fulfill content storage. In some situations, it is useful to use an NFS share to store this content. This appendix shows how to mount the NFS share on your Satellite Server's content management component. Important Use high-bandwidth, low-latency storage for the /var/lib/pulp file system. Red Hat Satellite has many I/O-intensive operations; therefore, high-latency, low-bandwidth storage might have issues with performance degradation. Procedure Create the NFS share. This example uses a share at nfs.example.com:/Satellite/pulp . Ensure this share provides the appropriate permissions to Satellite Server and its apache user. Stop Satellite services on your Satellite Server: Ensure Satellite Server has the nfs-utils package installed: You need to copy the existing contents of /var/lib/pulp to the NFS share. First, mount the NFS share to a temporary location: Copy the existing contents of /var/lib/pulp to the temporary location: Set the permissions for all files on the share to use the pulp user. Unmount the temporary storage location: Remove the existing contents of /var/lib/pulp : Edit the /etc/fstab file and add the following line: This makes the mount persistent across system reboots. Ensure to include the SELinux context. Enable the mount: Confirm the NFS share mounts to var/lib/pulp : Also confirm that the existing content exists at the mount on var/lib/pulp : Start Satellite services on your Satellite Server: Satellite Server now uses the NFS share to store content. Run a content synchronization to ensure the NFS share works as expected. For more information, see Section 6.6, "Synchronizing Repositories" .

Commands:
satellite-maintain service stop
satellite-maintain packages install nfs-utils
mkdir /mnt/temp mount -o rw nfs.example.com:/Satellite/pulp /mnt/temp
cp -r /var/lib/pulp/* /mnt/temp/.
umount /mnt/temp
rm -rf /var/lib/pulp/*
nfs.example.com:/Satellite/pulp /var/lib/pulp nfs rw,hard,intr,context="system_u:object_r:pulpcore_var_lib_t:s0"
mount -a
df Filesystem 1K-blocks Used Available Use% Mounted on nfs.example.com:/Satellite/pulp 309506048 58632800 235128224 20% /var/lib/pulp
ls /var/lib/pulp
satellite-maintain service start
3.16. Differences Between Red Hat Enterprise Linux 6 and 7 The RPM Package Manager in Red Hat Enterprise Linux 7 ships with a number of feature changes that are not available in the older version of the RPM Package Manager shipped with Red Hat Enterprise Linux 6. This section provides more details on the changes that may affect you when building your Software Collection packages for both systems. Differences in library support are detailed in Section 3.5.3, "Software Collection Library Support in Red Hat Enterprise Linux 7" . Differences in SELinux support are documented in Section 3.15.1, "SELinux Support in Red Hat Enterprise Linux 7" . 3.16.1. The %license Macro The %license macro allows you to specify the license file to be installed by your package. The macro is only supported by the RPM Package Manager in Red Hat Enterprise Linux 7. When building your Software Collection package on both Red Hat Enterprise Linux 6 and 7, declare the %license macro for Red Hat Enterprise Linux 6 as follows: %{!?_licensedir:%global license %%doc} 3.16.2. Missing runtime Subpackage Dependencies On Red Hat Enterprise Linux 7, the scl tool automatically generates the needed Requires on the Software Collection runtime subpackage. This does not work on Red Hat Enterprise Linux 6. When building your Software Collection for that system, you need to explicitly specify the dependency on the runtime subpackage in each Software Collection package: Requires: %{?scl_prefix}runtime 3.16.3. The scl-package() Provides By design, building a Software Collection package generates a number of Provide: scl-package() tags. The purpose of these is to internally identify the built package as belonging to a specific Software Collection. The tags are detailed in the following table. Table 3.2. Provides in Red Hat Enterprise Linux 7 Software Collection package Provide USD{software_collection_1} scl-package(software_collection_1) USD{software_collection_1}-build scl-package(software_collection_1) USD{software_collection_1}-runtime scl-package(software_collection_1) Red Hat Enterprise Linux 6 ships with an older version of the RPM Package Manager, so as an exception, building the same package on Red Hat Enterprise Linux 6 only generates a single Provide: scl-package() tag, as detailed in the following table. This is an expected behavior and the differences are handled internally by the scl tool. Table 3.3. Provide in Red Hat Enterprise Linux 6 Software Collection package Provide USD{software_collection_1} scl-package(software_collection_1) Do not use these internally generated dependencies to list packages that belong to a particular Software Collection. For information on how to properly list Software Collection packages, see Section 1.5, "Listing Installed Software Collections" .

Commands:
%{!?_licensedir:%global license %%doc}
Requires: %{?scl_prefix}runtime