mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5.2. How This Affects LVS Routing IPVS packet forwarding only allows connections in and out of the cluster based on it recognizing its port number or its firewall mark. If a client from outside the cluster attempts to open a port IPVS is not configured to handle, it drops the connection. Similarly, if the real server attempts to open a connection back out to the Internet on a port IPVS does not know about, it drops the connection. This means all connections from FTP clients on the Internet must have the same firewall mark assigned to them and all connections from the FTP server must be properly forwarded to the Internet using network packet filtering rules.

Commands:
2.40. RHEA-2011:0575 - new package: slapi-nis A new slapi-nis package is now available for Red Hat Enterprise Linux 6. The slapi-nis package provides two plug-ins for the 389 Directory Server and Red Hat Directory Server: The NIS Server plug-in allows a directory server to serve its data to clients using the NIS protocol. The Schema Compatibility plug-in allows a directory server to provide a modified view of a set of entries in a designated section of the directory. This enhancement update adds the slapi-nis package to Red Hat Enterprise Linux 6. (BZ# 643558 ) All users who require slapi-nis should install this new package.

Commands:
Chapter 3. Installation of Event-Driven Ansible controller Similar to the automation controller and automation hub components, the setup for Event-Driven Ansible controller includes default settings for specific variables in the inventory files. Important Event-Driven Ansible controller must be installed on a separate server and cannot be installed on the same host as automation hub and automation controller. Note If you are running Red Hat Enterprise Linux 8 and want to set your memory limits, you must have cgroup v2 enabled before you install Event-Driven Ansible. For specific instructions, see the Knowledge-Centered Support (KCS) article, Ansible Automation Platform Event-Driven Ansible controller for Red Hat Enterprise Linux 8 requires cgroupv2 . 3.1. Installing Event-Driven Ansible controller on Red Hat Ansible Automation Platform To prepare for installation of Event-Driven Ansible controller, review the following information in the Red Hat Ansible Automation Platform Planning Guide : Example Ansible Automation Platform architecture , including the Event-Driven Ansible controller Event-Driven Ansible controller general information Event-Driven Ansible controller system requirements When you are ready to install the Event-Driven Ansible controller, see the procedures in the Red Hat Ansible Automation Platform Installation Guide beginning with Chapter 3. Installing Red Hat Ansible Automation Platform . Lastly, see Appendix A. 5. Event-Driven Ansible controller variables in the Red Hat Ansible Automation Platform Installation Guide to view predefined variables for Event-Driven Ansible controller. 3.2. Deploying Event-Driven Ansible controller with Ansible Automation Platform Operator on OpenShift Container Platform Event-Driven Ansible is not limited to Ansible Automation Platform on VMs. You can also access this feature on Ansible Automation Platform Operator on OpenShift Container Platform. To deploy Event-Driven Ansible with Ansible Automation Platform Operator, follow the instructions in Deploying Event-Driven Ansible controller with Ansible Automation Platform Operator on OpenShift Container Platform . After successful deployment, you can connect to event sources and resolve issues more efficiently. Additional resources For more detailed information on planning, see the Red Hat Ansible Automation Platform Planning Guide . For a comprehensive list of predefined variables for the Event-Driven Ansible controller, see the Red Hat Ansible Automation Platform Installation Guide . For more information about deployment on Ansible Automation Platform operator, see the Deploying the Red Hat Ansible Automation Platform operator on OpenShift Container Platform Guide

Commands:
Chapter 11. Migrating from Red Hat Integration - AMQ Certificate Manager Operator Red Hat Integration - AMQ Certificate Manager Operator is not required to secure your connections, and will not be supported with OpenShift Container Platform 4.9. To secure connections on OpenShift Container Platform 4.9, you can remove the Red Hat Integration - AMQ Certificate Manager Operator as described below. Note After removing the Red Hat Integration - AMQ Certificate Manager Operator, the certificates that were previously issued continue to be valid and your connections are still secured. Prerequisites You are logged into the cluster using a cluster-admin account. Procedure Make sure you have upgraded the Red Hat Integration - AMQ Interconnect Operator to the latest version. Remove the Red Hat Integration - AMQ Certificate Manager Operator: In the OpenShift Container Platform web console, navigate to Operators OperatorHub . Choose Red Hat Integration - AMQ Certificate Manager Operator from the list of installed Operators, and then click Remove . Click OK when the following message is displayed: Remove the Red Hat Integration - AMQ Certificate Manager Operator CRD USD oc delete crd issuers.certmanager.k8s.io customresourcedefinition.apiextensions.k8s.io "issuers.certmanager.k8s.io" deleted Verify that all current connections are working. Note If you create new connections after removing the Red Hat Integration - AMQ Certificate Manager Operator, you must follow the procedure described in Section 2.1, "Creating secrets for SSL/TLS authentication" to secure the new connections. Revised on 2023-01-04 15:56:30 UTC

Commands:
Operator Red Hat Integration - AMQ Certificate Manager will be removed from all-namespaces, but any of its custom resource definitions or managed resources will remain. If your Operator deployed applications on the cluster or configured off-cluster resources, these will continue to run and require manual cleanup.
oc delete crd issuers.certmanager.k8s.io customresourcedefinition.apiextensions.k8s.io "issuers.certmanager.k8s.io" deleted
8.10.5. Examples Using Clock Synchronization Example 8.5. Clock synchronizing to local time with RTC and PIT timers In this example. the clock is synchronized to local time with RTC and PIT timers Note The PIT clocksource can be used with a 32-bit guest running under a 64-bit host (which cannot use PIT), with the following conditions: Guest virtual machine may have only one CPU APIC timer must be disabled (use the "noapictimer" command line option) NoHZ mode must be disabled in the guest (use the "nohz=off" command line option) High resolution timer mode must be disabled in the guest (use the "highres=off" command line option) The PIT clocksource is not compatible with either high resolution timer mode, or NoHz mode.

Commands:
<clock offset="localtime"> <timer name="rtc" tickpolicy="catchup" track="guest virtual machine" /> <timer name="pit" tickpolicy="delay" /> </clock>
4.6. The Metadata Daemon (lvmetad) LVM can optionally use a central metadata cache, implemented through a daemon ( lvmetad ) and a udev rule. The metadata daemon has two main purposes: It improves performance of LVM commands and it allows udev to automatically activate logical volumes or entire volume groups as they become available to the system. Note The lvmetad daemon is not currently supported across the nodes of a cluster, and requires that the locking type be local file-based locking. To take advantage of the daemon, you must do the following: Start the daemon through the lvm2-lvmetad service. To start the daemon automatically at boot time, use the chkconfig lvm2-lvmetad on command. To start the daemon manually, use the service lvm2-lvmetad start command. Configure LVM to make use of the daemon by setting the global/use_lvmetad variable to 1 in the lvm.conf configuration file. For information on the lvm.conf configuration file, see Appendix B, The LVM Configuration Files . Normally, each LVM command issues a disk scan to find all relevant physical volumes and to read volume group metadata. However, if the metadata daemon is running and enabled, this expensive scan can be skipped. Instead, the lvmetad daemon scans each device only once, when it becomes available, by means of udev rules. This can save a significant amount of I/O and reduce the time required to complete LVM operations, particularly on systems with many disks. For information on the udev device manager and udev rules, see Section A.3, "Device Mapper Support for the udev Device Manager" . When a new volume group is made available at runtime (for example, through hotplug or iSCSI), its logical volumes must be activated in order to be used. When the lvmetad daemon is enabled, the activation/auto_activation_volume_list option in the lvm.conf configuration file can be used to configure a list of volume groups and logical volumes that should be automatically activated. Without the lvmetad daemon, a manual activation is necessary. By default, this list is not defined, which means that all volumes are autoactivated once all of the physical volumes are in place. The autoactivation works recursively for LVM stacked on top of other devices, as it is event-based. Note When the lvmetad daemon is running, the filter = setting in the /etc/lvm/lvm.conf file does not apply when you execute the pvscan --cache device command. To filter devices, you need to use the global_filter = setting. Devices that fail the global filter are not opened by LVM and are never scanned. You may need to use a global filter, for example, when you use LVM devices in VMs and you do not want the contents of the devices in the VMs to be scanned by the physical host.

Commands:
4.45. DeviceKit-power 4.45.1. RHEA-2011:1276 - DeviceKit-power enhancement update Updated DeviceKit-power packages that add two enhancements are now available for Red Hat Enterprise Linux 6. DeviceKit-power provides a daemon, API and command line tools for managing power devices attached to the system. Enhancements BZ# 625880 To allow administrators easily disable the suspend and hibernate actions on the system, DeviceKit-power now checks the PolicyKit authorization before deciding whether an action can be completed. BZ# 727544 This update introduces a new sub-package DeviceKit-power-devel-docs, which contains developer's documentation for DeviceKit-power, so that it is now possible to install the DeviceKit-power-devel package on machines with multiple architectures without file conflicts. All users are advised to upgrade to these updated DeviceKit-power packages, which add these enhancements.

Commands:
3.4. Bridge A Bridge is a software device that uses packet forwarding in a packet-switched network. Bridging allows multiple network interface devices to share the connectivity of one NIC and appear on a network as separate physical devices. The bridge examines a packet's source addresses to determine relevant target addresses. Once the target address is determined, the bridge adds the location to a table for future reference. This allows a host to redirect network traffic to virtual machine associated VNICs that are members of a bridge. In Red Hat Virtualization a logical network is implemented using a bridge. It is the bridge rather than the physical interface on a host that receives an IP address. The IP address associated with the bridge is not required to be within the same subnet as the virtual machines that use the bridge for connectivity. If the bridge is assigned an IP address on the same subnet as the virtual machines that use it, the host is addressable within the logical network by virtual machines. As a rule it is not recommended to run network exposed services on a virtualization host. Guests are connected to a logical network by their VNICs, and the host is connected to remote elements of the logical network using its NIC. Each guest can have the IP address of its VNIC set independently, by DHCP or statically. Bridges can connect to objects outside the host, but such a connection is not mandatory. Custom properties can be defined for both the bridge and the Ethernet connection. VDSM passes the network definition and custom properties to the setup network hook script.

Commands:
5.205. nautilus 5.205.1. RHBA-2012:0914 - nautilus bug fix update Updated nautilus packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Nautilus is the file manager and graphical shell for the GNOME desktop that makes it easy to manage your files and the rest of your system. It allows to browse directories on local and remote file systems, preview files and launch applications associated with them. It is also responsible for handling the icons on the GNOME desktop. Bug Fixes BZ# 600260 When the display size was changed, no desktop folder refresh was performed. Consequently, icons disappeared outside the visible screen when the screen resolution was lowered. With this update, an explicit refresh action has been placed on screen size changes and the icons are now visible when the screen resolution is lowered. BZ# 782467 Previously, an empty file with the name ending ".desktop" was automatically identified as a special file. Consequently, some operations on the file, such as rename, failed. Now, a fallback that allows to use the regular file rename operation has been added to the code and these files can now be renamed as expected. BZ# 772103 Due to a short-lived internal object, free-space information was not displayed in the volume Properties dialog. With this update, a reference to another internal object has been placed in the code and the free-space information is now displayed properly. BZ# 755561 Previously, when the Nautilus desktop was set to display a user home directory, an internal queued load operation did not get canceled after refresh. Consequently, nautilus terminated unexpectedly on startup. With this update, pending internal operations that are not valid are correctly canceled and the crashes no longer occur. All users of nautilus are advised to upgrade to these updated packages, which fix these bugs.

Commands:
2.3. Storage Domain Types Red Hat Virtualization supports three types of storage domains, as well as the storage types that each storage domain supports. The Data Storage Domain stores the hard disk images of all virtual machines in the Red Hat Virtualization environment. Disk images may contain an installed operating system or data stored or generated by a virtual machine. Data storage domains support NFS, iSCSI, FCP, GlusterFS and POSIX compliant storage. A data domain cannot be shared between multiple data centers. The Export Storage Domain provides transitory storage for hard disk images and virtual machine templates being transferred between data centers. Additionally, export storage domains store backed up copies of virtual machines. Export storage domains support NFS storage. Multiple data centers can access a single export storage domain but only one data center can use it at a time. The ISO Storage Domain stores ISO files, also called images. ISO files are representations of physical CDs or DVDs. In the Red Hat Virtualization environment the common types of ISO files are operating system installation disks, application installation disks, and guest agent installation disks. These images can be attached to virtual machines and booted in the same way that physical disks are inserted into a disk drive and booted. ISO storage domains allow all hosts within the data center to share ISOs, eliminating the need for physical optical media.

Commands:
5.220. openmotif 5.220.1. RHBA-2012:1405 - openmotif bug fix update Updated openmotif packages that fix three bugs is now available for Red Hat Enterprise Linux 6. The openmotif packages include the Motif shared libraries needed to run applications, which are dynamically linked against Motif, as well as MWM, the Motif Window Manager. Bug Fixes BZ# 866499 Under certain circumstances, closing an application using a text or a combo box widget could result in an invalid memory access for widgets that were already destroyed. A patch has been provided to address this issue and freed memory is no longer accessed in the described scenario. BZ# 866496 Prior to this update, the insertion cursor of a text widget could have a shadow border line under certain settings. This bug has been fixed and the cursor now displays correctly at all times. BZ# 867463 Due to 32-bit time stamp issues, attempting to copy and paste on a 64-bit architecture using the clipboard could fail occasionally. With this update, the underlying source code has been modified to ensure the time stamp always contains a "CARD32" value, so that copy and paste on 64-bit architectures works as expected. Users of openmotif are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Preface Red Hat OpenShift Container Storage 4.6 supports deployment on existing Red Hat OpenShift Container Platform (RHOCP) using Red Hat OpenStack Platform clusters. Note Both internal and external Openshift Container Storage clusters are supported on Red Hat OpenStack Platform. See Planning your deployment for more information about deployment requirements. To deploy OpenShift Container Storage, follow the appropriate deployment process for your environment: Internal mode Deploying OpenShift Container Storage on Red Hat OpenStack Platform in internal mode . External mode Deploying OpenShift Container Storage on Red Hat OpenStack Platform in external mode

Commands:
11.2.3. Required ifcfg Options for Linux on System z NETTYPE = answer where answer is one of the following: ctc - Channel-to-Channel communication. For point-to-point TCP/IP or TTY. lcs - LAN Channel Station (LCS). qeth - QETH (QDIO Ethernet). This is the default network interface. It is the preferred installation method for supporting real or virtual OSA cards and HiperSockets devices.

Commands:
Chapter 5. System requirements Use this information when planning your Red Hat Ansible Automation Platform installations and designing automation mesh topologies that fit your use case. Prerequisites You can obtain root access either through the sudo command, or through privilege escalation. For more on privilege escalation, see Understanding privilege escalation . You can de-escalate privileges from root to users such as: AWX, PostgreSQL, Event-Driven Ansible, or Pulp. You have configured an NTP client on all nodes. 5.1. System requirements for RPM installation For system requirements for the RPM installation method of Ansible Automation Platform, see the System requirements section of RPM installation . 5.2. System requirements for containerized installation For system requirements for the containerized installation method of Ansible Automation Platform, see the System requirements section of Containerized installation . 5.3. System requirements for installing on OpenShift Container Platform For system requirements for installing Ansible Automation Platform on OpenShift Container Platform, see the Tested system configurations section of Tested deployment models .

Commands:
Chapter 4. Creating a Custom Puppet Environment You can create a Puppet environment within your Satellite. Procedure In the Satellite web UI, navigate to Configure > Puppet Environments . Click Create Puppet Environment to create a Puppet environment. Enter a Name , alphanumeric characters and underscores are allowed, such as example_environment . Optional: Set a location context. Optional: Set an organization context. Click Submit to create the Puppet environment. Note that before you run an import of Puppet modules into Satellite, the environment must already exist as the folder /etc/puppetlabs/code/environments/ example_environment on the Puppet server and contain installed Puppet modules.

Commands:
4.7.3. GFS Directory Attribute The gfs_tool command can be used to assign (set) a direct I/O attribute flag, inherit_directio , to a GFS directory. Enabling the inherit_directio flag on a directory causes all newly created regular files in that directory to automatically inherit the directio flag. Also, the inherit_directio flag is inherited by any new subdirectories created in the directory. The inherit_directio flag can also be cleared. Usage Setting the inherit_directio flag Clearing the inherit_directio flag Directory Specifies the directory where the inherit_directio flag is set. Example In this example, the command sets the inherit_directio flag on the directory named /gfs1/data/ .

Commands:
gfs_tool setflag inherit_directio Directory
gfs_tool clearflag inherit_directio Directory
gfs_tool setflag inherit_directio /gfs1/data/
5.2. virt-manager virt-manager is a lightweight graphical tool for managing virtual machines, more user-friendly and less powerful than virsh . It provides the ability to control the life cycle of existing machines, provision new machines, manage virtual networks, access the graphical console of virtual machines, and view performance statistics. For a demonstration of using virt-manager , see Section 4.3, "Creating a Virtual Machine with Virtual Machine Manager" . This tool is provided by the virt-manager package. Note Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information about managing virtual machines with virt-manager .

Commands:
7.164. OpenIPMI 7.164.1. RHBA-2013:0492 - OpenIPMI bug fix update Updated OpenIPMI packages that fix one bug are now available for Red Hat Enterprise Linux 6. The OpenIPMI packages provide command-line tools and utilities to access platform information using Intelligent Platform Management Interface (IPMI). System administrators can use OpenIPMI to manage systems and to perform system health monitoring. Bug Fix BZ#881450 The kernel ipmi_msghandler and ipmi_si modules are no longer delivered as standalone modules. As a consequence, an error occurred if these modules were used independently. With this update, the OpenIPMI init script has been modified to enable IPMI service operations on a kernel with ipmi_si and ipmi_msghandler statically compiled in the kernel. Also, the service status message now includes a new "in kernel" module state. Users of OpenIPMI are advised to upgrade to these updated packages, which fix this bug.

Commands: