mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 23. Removing a Subsystem Removing a subsystem requires specifying the subsystem type and the name of the server in which the subsystem is running. This command removes all files associated with the subsystem (without removing the subsystem packages). The -s option specifies the subsystem to be removed (such as CA, KRA, OCSP, TKS, or TPS). The -i option specifies the instance name, such as pki-tomcat . Example 23.1. Removing a CA Subsystem The pkidestroy utility removes the subsystem and any related files, such as the certificate databases, certificates, keys, and associated users. It does not uninstall the subsystem packages. If the subsystem is the last subsystem on the server instance, the server instance is removed as well.

Commands:
pkidestroy -s subsystem_type -i instance_name
pkidestroy -s CA -i pki-tomcat Loading deployment configuration from /var/lib/pki/pki-tomcat/ca/registry/ca/deployment.cfg. Uninstalling CA from /var/lib/pki/pki-tomcat. Removed symlink /etc/systemd/system/multi-user.target.wants/pki-tomcatd.target. Uninstallation complete.
Chapter 2. Setting up RHEL image builder Use RHEL image builder to create your customized RHEL for Edge images. After you install RHEL image builder on a RHEL system, RHEL image builder is available as an application in RHEL web console. You can also access RHEL image builder on the command line by using the composer-cli tool. Note It is recommended to install RHEL image builder on a virtual machine. 2.1. Image builder system requirements The environment where RHEL image builder runs, for example a virtual machine, must meet the requirements that are listed in the following table. Note Running RHEL image builder inside a container is not supported. Table 2.1. Image builder system requirements Parameter Minimal Required Value System type A dedicated virtual machine Processor 2 cores Memory 4 GiB Disk space 20 GiB Access privileges Administrator level (root) Network Connectivity to Internet Note The 20 GiB disk space requirement is enough to install and run RHEL image builder in the host. To build and deploy image builds, you must allocate additional dedicated disk space. 2.2. Installing RHEL image builder To install RHEL image builder on a dedicated virtual machine, follow these steps: Prerequisites The virtual machine is created and is powered on. You have installed RHEL and you have subscribed to RHSM or Red Hat Satellite. You have enabled the BaseOS and AppStream repositories to be able to install the RHEL image builder packages. Procedure Install the following packages on the virtual machine. osbuild-composer composer-cli cockpit-composer bash-completion firewalld RHEL image builder is installed as an application in RHEL web console. Reboot the virtual machine Configure the system firewall to allow access to the web console: Enable RHEL image builder. The osbuild-composer and cockpit services start automatically on first access. Load the shell configuration script so that the autocomplete feature for the composer-cli command starts working immediately without reboot: Additional resources Managing repositories

Commands:
dnf install osbuild-composer composer-cli cockpit-composer bash-completion firewalld
firewall-cmd --add-service=cockpit && firewall-cmd --add-service=cockpit --permanent
systemctl enable osbuild-composer.socket cockpit.socket --now
source /etc/bash_completion.d/composer-cli
Chapter 9. Removing the Red Hat build of OpenTelemetry The steps for removing the Red Hat build of OpenTelemetry from an OpenShift Container Platform cluster are as follows: Shut down all Red Hat build of OpenTelemetry pods. Remove any OpenTelemetryCollector instances. Remove the Red Hat build of OpenTelemetry Operator. 9.1. Removing an OpenTelemetry Collector instance by using the web console You can remove an OpenTelemetry Collector instance in the Administrator view of the web console. Prerequisites You are logged in to the web console as a cluster administrator with the cluster-admin role. For Red Hat OpenShift Dedicated, you must be logged in using an account with the dedicated-admin role. Procedure Go to Operators Installed Operators Red Hat build of OpenTelemetry Operator OpenTelemetryInstrumentation or OpenTelemetryCollector . To remove the relevant instance, select Delete ... Delete . Optional: Remove the Red Hat build of OpenTelemetry Operator. 9.2. Removing an OpenTelemetry Collector instance by using the CLI You can remove an OpenTelemetry Collector instance on the command line. Prerequisites An active OpenShift CLI ( oc ) session by a cluster administrator with the cluster-admin role. Tip Ensure that your OpenShift CLI ( oc ) version is up to date and matches your OpenShift Container Platform version. Run oc login : USD oc login --username=<your_username> Procedure Get the name of the OpenTelemetry Collector instance by running the following command: USD oc get deployments -n <project_of_opentelemetry_instance> Remove the OpenTelemetry Collector instance by running the following command: USD oc delete opentelemetrycollectors <opentelemetry_instance_name> -n <project_of_opentelemetry_instance> Optional: Remove the Red Hat build of OpenTelemetry Operator. Verification To verify successful removal of the OpenTelemetry Collector instance, run oc get deployments again: USD oc get deployments -n <project_of_opentelemetry_instance> 9.3. Additional resources Deleting Operators from a cluster Getting started with the OpenShift CLI

Commands:
oc login --username=<your_username>
oc get deployments -n <project_of_opentelemetry_instance>
oc delete opentelemetrycollectors <opentelemetry_instance_name> -n <project_of_opentelemetry_instance>
oc get deployments -n <project_of_opentelemetry_instance>
20.7. Deauthorizing a Client To revoke the authorization of a client to access the Red Hat Gluster Storage trusted storage pool, you can do any of the following: Remove an authorized client from the allowed list Revoke SSL/TLS certificate authorization through a certificate revocation list (CRL) 20.7.1. To Remove an Authorized Client From the Allowed List Procedure 20.12. Removing an authorized client from the allowed list List currently authorized clients and servers For example, the following command shows that there are three authorized servers and five authorized clients. Remove clients to deauthorize from the output For example, if you want to deauthorize client2 and client4, copy the string and remove those clients from the list. Set the new list of authorized clients and servers Set the value of auth.ssl-allow to your updated string. For example, the updated list shows three servers and three clients. 20.7.2. To Revoke SSL/TLS Certificate Authorization Using a SSL Certificate Revocation List To protect the cluster from malicious or unauthorized network entities, you can specify a path to a directory containing SSL certificate revocation list (CRL) using the ssl.crl-path option. The path containing the list of revoked certificates enables server nodes to stop the nodes with revoked certificates from accessing the cluster. For example, you can provide the path to a directory containing CRL with the volume set command as follows: Note Only the CA signed certificates can be revoked and not the self-signed certificates To set up the CRL files, perform the following: Copy the CRL files to a directory. Change directory to the directory containing CRL files. Compute hashes to the CRL files using the c_rehash utility. The hash and symbolic linking can be done using the c_rehash utility, which is available through the openssl-perl RPM. The name of the symbolic link must be the hash of the Common Name. For more information, see the crl man page. Set the ssl.crl-path volume option. where, path-to-directory has to be an absolute name of the directory that hosts the CRL files.

Commands:
gluster volume get VOLNAME auth.ssl-allow
gluster volume get sample_volname auth.ssl-allow server1,server2,server3,client1,client2,client3,client4,client5
server1,server2,server3,client1,client3,client5
gluster volume set VOLNAME auth.ssl-allow <list_of_systems>
gluster volume set sample_volname auth.ssl-allow server1,server2,server3,client1,client3,client5
gluster volume set vm-images ssl.crl-path /etc/ssl/
c_rehash .
gluster volume set VOLNAME ssl.crl-path path-to-directory
function::sprint_usyms Name function::sprint_usyms - Return stack for user addresses from string Synopsis Arguments callers String with list of hexadecimal (user) addresses Description Perform a symbolic lookup of the addresses in the given string, which are assumed to be the result of a prior calls to ustack , ucallers , and similar functions. Returns a simple backtrace from the given hex string. One line per address. Includes the symbol name (or hex address if symbol couldn't be resolved) and module name (if found), as obtained from usymdata . Includes the offset from the start of the function if found, otherwise the offset will be added to the module (if found, between brackets). Returns the backtrace as string (each line terminated by a newline character). Note that the returned stack will be truncated to MAXSTRINGLEN, to print fuller and richer stacks use print_usyms .

Commands:
sprint_usyms(callers:string)
8.159. pyparted 8.159.1. RHBA-2013:1616 - pyparted bug fix update Updated pyparted packages that fix one bug are now available for Red Hat Enterprise Linux 6. The pyparted packages contain Python bindings for the libparted library. They are primarily used by the Red Hat Enterprise Linux installation software. Bug Fix BZ# 896024 Due to a bug in the underlying source code, an attempt to run the parted.version() function caused a system error to be returned. This bug has been fixed and parted.version() can now be executed as expected. Users of pyparted are advised to upgrade to these updated packages, which fix this bug.

Commands:
9.2. ia64 Architectures Bugzilla #453033 On some SGI Altix systems that feature the IOC4 multi-function device, you may encounter problems when using attached IDE devices (such as CD-ROM drives). This is caused by a bug in the sgiioc4 IDE driver, which prevents some devices from being detected properly on system boot. You can work around this bug by manually loading the driver, which in turn allows attached IDE devices to be detected properly. To do so, run the following command as root: /sbin/modprobe sgiioc4

Commands:
4.43. cyrus-sasl 4.43.1. RHBA-2011:1687 - cyrus-sasl bug fix and enhancement update Updated cyrus-sasl packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The cyrus-sasl packages contain the Cyrus implementation of the Simple Authentication and Security Layer (SASL), a method for adding authentication support to connection-based protocols. Bug Fixes BZ# 720451 Prior to this update, the ntlm plug-in did not work due to a code error. This update modifies the source code so that the plug-in now works as expected. BZ# 730242 Prior to this update, creating the user ID and the group ID of the saslauth daemon caused conflicts. This update corrects this behavior and now the saslauth daemon works as expected. BZ# 730246 Prior to this update, cyrus-sasl displayed redundant warnings during the compilation. With this update, cyrus-sasl has been modified and now works as expected. Enhancement BZ# 727274 This update adds support of partial Relocation Read-Only (RELRO) for the cyrus-sasl libraries. All users of cyrus-sasl are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 5. Using the Nexus Repository Manager plugin The Nexus Repository Manager plugin displays the information about your build artifacts in your Developer Hub application. The build artifacts are available in the Nexus Repository Manager. Important The Nexus Repository Manager plugin is 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. The Nexus Repository Manager is a front-end plugin that enables you to view the information about build artifacts. Prerequisites Your Developer Hub application is installed and running. You have installed the Nexus Repository Manager plugin. Procedure Open your Developer Hub application and select a component from the Catalog page. Go to the BUILD ARTIFACTS tab. The BUILD ARTIFACTS tab contains a list of build artifacts and related information, such as VERSION , REPOSITORY , REPOSITORY TYPE , MANIFEST , MODIFIED , and SIZE .

Commands:
8.79. java-1.6.0-openjdk 8.79.1. RHBA-2013:1741 - java-1.6.0-openjdk bug fix and enhancement update Updated java-1.6.0-openjdk packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The java-1.6.0-openjdk packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Java Software Development Kit. Note The java-1.6.0-openjdk packages have been upgraded to upstream IcedTea version 1.13.0, which provides a number of bug fixes and enhancements over the version. (BZ# 983411 ) Bug Fix BZ# 976897 Previously, int[] objects allocated by instances of the com.sun.imageio.plugins.jpeg.JPEGImageWriter class were consuming extensive amounts of memory, which was consequently not released. With this update, the underlying stream processing logic has been modified to ensure correct releasing of such memory, and extensive memory consumption no longer occurs. Users of java-1.6.0-openjdk are advised to upgrade to these updated packages, which fix these bugs and add these enhancements. All running instances of OpenJDK Java must be restarted for the update to take effect.

Commands:
7.289. xorg-x11-xkb-utils 7.289.1. RHBA-2013:0305 - xorg-x11-xkb-utils bug fix and enhancement update Updated xorg-x11-xkb-utils packages that fix several bugs and add various enhancements are now available. The x11-xkb-utils packages provide a set of client-side utilities for XKB, the X11 keyboard extension. Note The x11-xkb-utils packages have been upgraded to upstream version 7.7, which provides a number of bug fixes and enhancements over the version. (BZ# 835282 , BZ# 872057 ) All users of x11-xkb-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Part I. Viewing and managing your subscription inventory The Subscription Inventory page on the Red Hat Hybrid Cloud Console provides information and resources to help you manage the account-level subscriptions in your inventory. Specifically, you can view details and status information about each subscription, learn more about subscriptions and how to manage them, and explore purchasing and no-cost trial options. Subscription-level details (name, SKU, quantity, and service level) about each subscription in your inventory are presented in the All subscriptions table. These details, plus the account support type and subscription capacity, are also presented in a list on the subscription details page. The account number is displayed in the table title. The subscription status types (Active, Expired, Expiring soon, and Future dated) and the number of subscriptions in your inventory with each status are displayed in a set of tiles on the Subscription inventory page. There are multiple ways to view and organize the subscription information in the All subscriptions table. You can use the table to sort the subscriptions alphabetically or numerically by name, SKU, quantity, or service level. You can use the tiles to filter your subscriptions by status (active, expired, expiring soon, or future dated). You can use the search bar to filter your subscriptions by name or SKU. Authorized users can use the Subscription Inventory page to manage your subscriptions and interact with your Red Hat account team, as needed, to maintain adequate subscription quantities and types for your account.

Commands:
Removing OpenShift Serverless Red Hat OpenShift Serverless 1.35 Removing Serverless from your cluster Red Hat OpenShift Documentation Team

Commands:
oc delete knativeeventings.operator.knative.dev knative-eventing -n knative-eventing
oc delete namespace knative-eventing
oc delete knativeservings.operator.knative.dev knative-serving -n knative-serving
oc delete namespace knative-serving
oc get crd -oname | grep 'knative.dev' | xargs oc delete
2.2.8.4. Disable Sendmail Network Listening By default, Sendmail is set up to only listen to the local loopback address. You can verify this by viewing the file /etc/mail/sendmail.mc to ensure that the following line appears: This ensures that Sendmail only accepts mail messages (such as cron job reports) from the local system and not from the network. This is the default setting and protects Sendmail from a network attack. For removal of the localhost restriction, the Addr=127.0.0.1 string needs to be removed. Changing Sendmail's configuration requires installing the sendmail-cf package, then editing the .mc file, running /etc/mail/make and finally restarting sendmail . The .cf configuration file will be regenerated. Note that the system clock must be correct and working and that there must not be any system clock time shifts between these actions in order for the configuration file to be automatically regenerated.

Commands:
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
3.3. Converting a virtual machine Once you have prepared to convert the virtual machines, use virt-v2v to perform the actual conversions. This section provides the steps to convert the virtual machines, and the command syntax for virt-v2v . Note that conversions are resource intensive processes that require copying the whole disk image for a virtual machine. In typical environments, converting a single virtual machine takes approximately 5-10 minutes. In Example 3.4, "Typical virt-v2v conversion time" a virtual machine with a single 8GB disk is copied over SSH on a 1GigE network on three-year-old consumer hardware: Example 3.4. Typical virt-v2v conversion time The size of the disk to be copied is the major factor in determining conversion time. For a virtual machine on average hardware with a single disk of 20GB or less, a conversion usually takes less than 10 minutes. 3.3.1. Converting a local virtual machine using virt-v2v virt-v2v converts virtual machines from a foreign hypervisor to run on KVM, managed by libvirt. The general command syntax for converting machines to run on KVM, managed by libvirt is: For a list of virt-v2v parameters, refer to Chapter 7, References .

Commands:
win2k3r2-pv-32.img: 100% [===========================================]D 0h02m57s virt-v2v: win2k3r2-pv-32 configured with virtio drivers.
virt-v2v -i libvirtxml -op pool --bridge bridge_name guest_name.xml virt-v2v -op pool --network netname guest_name virt-v2v -ic esx://esx.example.com/?no_verify=1 -op pool --bridge bridge_name guest_name
Chapter 1. Enhancements ENTMQIC-2455 - Allow AMQP open properties to be supplemented from connector configuration With this release you can now add metadata when connecting routers, as described in Adding metadata to connections . ENTMQIC-2448 - Allow defining address prefix shared by different multitenant listeners With this release a multitenant prefix specified by a vhost policy can be shared among several hostnames with a pattern specified in the aliases parameter as described in Creating vhost policies .

Commands:
14.9.5. Forcing a Guest Virtual Machine to Stop Force a guest virtual machine to stop with the virsh destroy command: This command does an immediate ungraceful shutdown and stops the specified guest virtual machine. Using virsh destroy can corrupt guest virtual machine file systems. Use the destroy option only when the guest virtual machine is unresponsive. If you want to initiate a graceful shutdown, use the virsh destroy --graceful command.

Commands:
virsh destroy {domain-id, domain-name or domain-uuid} [--graceful]
Chapter 6. Managing Satellite with Ansible collections Satellite Ansible Collections is a set of Ansible modules that interact with the Satellite API. You can manage and automate many aspects of Satellite with Satellite Ansible collections. 6.1. Installing the Satellite Ansible modules Use this procedure to install the Satellite Ansible modules. Procedure Install the package using the following command: 6.2. Viewing the Satellite Ansible modules You can view the installed Satellite Ansible modules by running: Alternatively, you can also see the complete list of Satellite Ansible modules and other related information at Red Hat Ansible Automation Platform . All modules are in the redhat.satellite namespace and can be referred to in the format redhat.satellite._module_name_ . For example, to display information about the activation_key module, enter the following command:

Commands:
satellite-maintain packages install ansible-collection-redhat-satellite
ansible-doc -l redhat.satellite
ansible-doc redhat.satellite.activation_key
4.4. Results Translation Extension The JDBCExecutionFactory provides several methods to modify the java.sql.Statement and java.sql.ResultSet interactions, including: Overriding the createXXXExecution to subclass the corresponding JDBCXXXExecution. The JDBCBaseExecution has protected methods to get the appropriate statement (getStatement, getPreparedStatement, getCallableStatement) and to bind prepared statement values bindPreparedStatementValues. Retrieve values from the JDBC ResultSet or CallableStatement - see the retrieveValue methods.

Commands:
7.17. bridge-utils 7.17.1. RHEA-2013:0322 - bridge-utils enhancement update Updated bridge-utils packages that add two enhancements are now available for Red Hat Enterprise Linux 6. The bridge-utils packages contain utilities for configuration of the Linux Ethernet bridge. The Linux Ethernet bridge can be used to connect multiple Ethernet devices together. This connection is fully transparent: hosts connected to one Ethernet device see hosts connected to the other Ethernet devices directly. Enhancements BZ# 676355 The man page was missing the multicast option descriptions. This update adds that information to the man page. BZ#690529 This enhancement adds the missing feature described in the BRCTL(8) man page, that allows the user to get the bridge information for a simple bridge using the "brctl show USDBRIDGE" command. All users of bridge-utils are advise to upgrade to these updated packages, which add these enhancements.

Commands:
B.17.2.4. Typographical errors in tags Symptom The following error message appears: Investigation XML errors are easily caused by a simple typographical error. This error message highlights the XML error - in this case, an extra white space within the word type - with a pointer. These XML examples will not parse correctly because of typographical errors such as a missing special character, or an additional character: Solution To identify the problematic tag, read the error message for the context of the file, and locate the error with the pointer. Correct the XML and save the changes.

Commands:
error: (name_of_guest.xml):1: Specification mandate value for attribute ty <domain ty pe='kvm'> -----------^
<domain ty pe='kvm'>
<domain type 'kvm'>
<dom#ain type='kvm'>