mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 6. Known Issues 6.1. Installation anaconda component To automatically create an appropriate partition table on disks that are uninitialized or contain unrecognized formatting, use the zerombr kickstart command. The --initlabel option of the clearpart command is not intended to serve this purpose. anaconda component On s390x systems, you cannot use automatic partitioning and encryption. If you want to use storage encryption, you must perform custom partitioning. Do not place the /boot volume on an encrypted volume. anaconda component The order of device names assigned to USB attached storage devices is not guaranteed. Certain USB attached storage devices may take longer to initialize than others, which can result in the device receiving a different name than you expect (for example, sdc instead of sda ). During installation, verify the storage device size, name, and type when configuring partitions and file systems. anaconda component The kdump default on feature currently depends on Anaconda to insert the crashkernel= parameter to the kernel parameter list in the boot loader's configuration file. anaconda component, BZ# 623261 In some circumstances, disks that contain a whole disk format (for example, an LVM Physical Volume populating a whole disk) are not cleared correctly using the clearpart --initlabel kickstart command. Adding the --all switch-as in clearpart --initlabel --all -ensures disks are cleared correctly. anaconda component When installing on the IBM System z architecture, if the installation is being performed over SSH, avoid resizing the terminal window containing the SSH session. If the terminal window is resized during the installation, the installer will exit and the installation will terminate. yaboot component, BZ# 613929 The kernel image provided on the CD/DVD is too large for Open Firmware. Consequently, on the POWER architecture, directly booting the kernel image over a network from the CD/DVD is not possible. Instead, use yaboot to boot from a network. anaconda component The Anaconda partition editing interface includes a button labeled Resize . This feature is intended for users wishing to shrink an existing file system and an underlying volume to make room for an installation of a new system. Users performing manual partitioning cannot use the Resize button to change sizes of partitions as they create them. If you determine a partition needs to be larger than you initially created it, you must delete the first one in the partitioning editor and create a new one with the larger size. system-config-kickstart component Channel IDs (read, write, data) for network devices are required for defining and configuring network devices on IBM S/390 systems. However, system-config-kickstart -the graphical user interface for generating a kickstart configuration-cannot define channel IDs for a network device. To work around this issue, manually edit the kickstart configuration that system-config-kickstart generates to include the desired network devices.

Commands:
5.7. Viewing Virtual Machines Pinned to a Host You can view virtual machines pinned to a host even while the virtual machines are offline. Use the Pinned to Host list to see which virtual machines will be affected and which virtual machines will require a manual restart after the host becomes active again. Viewing Virtual Machines Pinned to a Host Click Compute Hosts . Click a host name to go to the details view. Click the Virtual Machines tab. Click Pinned to Host .

Commands:
Chapter 1. Preface This document provides an overview of differences between two major versions of Red Hat Enterprise Linux: RHEL 8 and RHEL 9. It provides a list of changes relevant for evaluating an upgrade to RHEL 9 rather than an exhaustive list of all alterations. For details regarding RHEL 9 usage, see the RHEL 9 product documentation . For guidance regarding an in-place upgrade from RHEL 8 to RHEL 9, see Upgrading from RHEL 8 to RHEL 9 . For information about major differences between RHEL 7 and RHEL 8, see Considerations in adopting RHEL 8 . Capabilities and limits of Red Hat Enterprise Linux 9 as compared to other versions of the system are available in the Knowledgebase article Red Hat Enterprise Linux technology capabilities and limits . Information regarding the Red Hat Enterprise Linux life cycle is provided in the Red Hat Enterprise Linux Life Cycle document. The Package manifest document provides a package listing for RHEL 9, including licenses and application compatibility levels. Application compatibility levels are explained in the Red Hat Enterprise Linux 9: Application Compatibility Guide document.

Commands:
Chapter 15. Changing resources for the OpenShift Data Foundation components When you install OpenShift Data Foundation, it comes with pre-defined resources that the OpenShift Data Foundation pods can consume. In some situations with higher I/O load, it might be required to increase these limits. To change the CPU and memory resources on the rook-ceph pods, see Section 15.1, "Changing the CPU and memory resources on the rook-ceph pods" . To tune the resources for the Multicloud Object Gateway (MCG), see Section 15.2, "Tuning the resources for the MCG" . 15.1. Changing the CPU and memory resources on the rook-ceph pods When you install OpenShift Data Foundation, it comes with pre-defined CPU and memory resources for the rook-ceph pods. You can manually increase these values according to the requirements. You can change the CPU and memory resources on the following pods: mgr mds rgw The following example illustrates how to change the CPU and memory resources on the rook-ceph pods. In this example, the existing MDS pod values of cpu and memory are increased from 1 and 4Gi to 2 and 8Gi respectively. Edit the storage cluster: <storagecluster_name> Specify the name of the storage cluster. For example: Add the following lines to the storage cluster Custom Resource (CR): Save the changes and exit the editor. Alternatively, run the oc patch command to change the CPU and memory value of the mds pod: <storagecluster_name> Specify the name of the storage cluster. For example: 15.2. Tuning the resources for the MCG The default configuration for the Multicloud Object Gateway (MCG) is optimized for low resource consumption and not performance. For more information on how to tune the resources for the MCG, see the Red Hat Knowledgebase solution Performance tuning guide for Multicloud Object Gateway (NooBaa) .

Commands:
oc edit storagecluster -n openshift-storage <storagecluster_name>
oc edit storagecluster -n openshift-storage ocs-storagecluster
spec: resources: mds: limits: cpu: 2 memory: 8Gi requests: cpu: 2 memory: 8Gi
oc patch -n openshift-storage storagecluster <storagecluster_name> --type merge --patch '{"spec": {"resources": {"mds": {"limits": {"cpu": "2","memory": "8Gi"},"requests": {"cpu": "2","memory": "8Gi"}}}}}'
oc patch -n openshift-storage storagecluster ocs-storagecluster --type merge --patch ' {"spec": {"resources": {"mds": {"limits": {"cpu": "2","memory": "8Gi"},"requests": {"cpu": "2","memory": "8Gi"}}}}} '
5.2.22. /proc/mounts This file provides a list of all mounts in use by the system: The output found here is similar to the contents of /etc/mtab , except that /proc/mount is more up-to-date. The first column specifies the device that is mounted, the second column reveals the mount point, and the third column tells the file system type, and the fourth column tells you if it is mounted read-only ( ro ) or read-write ( rw ). The fifth and sixth columns are dummy values designed to match the format used in /etc/mtab .

Commands:
rootfs / rootfs rw 0 0 /proc /proc proc rw,nodiratime 0 0 none /dev ramfs rw 0 0 /dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0 none /dev ramfs rw 0 0 /proc /proc proc rw,nodiratime 0 0 /sys /sys sysfs rw 0 0 none /dev/pts devpts rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 /dev/hda1 /boot ext3 rw 0 0 none /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
20.4. Connecting to the Hypervisor with virsh Connect The virsh connect [ hostname-or-URI ] [--readonly] command begins a local hypervisor session using virsh. After the first time you run this command it will run automatically each time the virsh shell runs. The hypervisor connection URI specifies how to connect to the hypervisor. The most commonly used URIs are: qemu:///system - connects locally as the root user to the daemon supervising guest virtual machines on the KVM hypervisor. qemu:///session - connects locally as a user to the user's set of guest local machines using the KVM hypervisor. lxc:/// - connects to a local Linux container. The command can be run as follows, with the target guest being specified either either by its machine name (hostname) or the URL of the hypervisor (the output of the virsh uri command), as shown: For example, to establish a session to connect to your set of guest virtual machines, with you as the local user: To initiate a read-only connection, append the above command with --readonly . For more information on URIs, see Remote URIs . If you are unsure of the URI, the virsh uri command will display it:

Commands:
virsh uri qemu:///session
virsh connect qemu:///session
Appendix A. Using Your Subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2022-02-01 16:35:06 UTC

Commands:
5.118. iscsi-initiator-utils 5.118.1. RHBA-2012:0957 - iscsi-initiator-utils bug fix and enhancement update Updated iscsi-initiator-utils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The iscsi-initiator-utils package provides the server daemon for the iSCSI protocol, as well as utilities used to manage the daemon. iSCSI is a protocol for distributed disk access using SCSI commands sent over Internet Protocol networks. The iscsiuio tool has been upgraded to upstream version 0.7.2.1, which provides a number of bug fixes and one enhancement over the version. (BZ# 740054 ) Bug Fixes BZ# 738192 The iscsistart utility used hard-coded values as its settings. Consequently, it could take several minutes before change failure detection and path failover when using dm-multipath took place. With this update, the iscsistart utility has been modified to process settings provided on the command line. BZ# 739049 The iSCSI README file incorrectly listed the --info option as the option to display iscsiadm iSCSI information. The README has been corrected and it now states correctly that you need to use the "-P 1" argument to obtain such information. BZ# 739843 The iSCSI discovery process via a TOE (TCP Offload Engine) interface failed if the "iscsiadm -m iface" command had not been executed. This happened because the "iscsiadm -m" discovery command did not check interface settings. With this update, the iscsiadm tool creates the default ifaces settings when first used and the problem no longer occurs. BZ# 796574 If the port number was passed with a non-fully-qualified hostname to the iscsiadm tool, the tool created records with the port being part of the hostname. Consequently, the login or discovery operation failed because iscsiadm was not able to find the record. With this update, the iscsiadm portal parser has been modified to separate the port from the hostname. As a result, the port is parsed and processed correctly. Enhancement BZ# 790609 The iscsidm tool has been updated to support the ping command using QLogic's iSCSI offload cards and to manage the CHAP (Challenge-Handshake Authentication Protocol) entries on the host. All users of iscsi-initiator-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
probe::tcp.receive Name probe::tcp.receive - Called when a TCP packet is received Synopsis tcp.receive Values psh TCP PSH flag ack TCP ACK flag daddr A string representing the destination IP address syn TCP SYN flag rst TCP RST flag sport TCP source port protocol Packet protocol from driver urg TCP URG flag name Name of the probe point family IP address family fin TCP FIN flag saddr A string representing the source IP address iphdr IP header address dport TCP destination port

Commands:
Part II. Technology Previews This chapter provides a list of all available Technology Previews in Red Hat Enterprise Linux 6.8. Technology Preview features are currently not supported under Red Hat Enterprise Linux subscription services, may not be functionally complete, and are generally not suitable for production use. However, these features are included as a customer convenience and to provide the feature with wider exposure. Customers may find these features useful in a non-production environment. Customers are also free to provide feedback and functionality suggestions for a Technology Preview feature before it becomes fully supported. Errata will be provided for high-severity security issues. During the development of a Technology Preview feature, additional components may become available to the public for testing. It is the intention of Red Hat clustering to fully support Technology Preview features in a future release. For information about the Technology Preview features support scope, see https://access.redhat.com/support/offerings/techpreview/ .

Commands:
6.8. Attaching a Red Hat Subscription and Enabling the Certificate System Package Repository Before you can install and update Certificate System, you must enable the corresponding repository: Attach the Red Hat subscriptions to the system: Skip this step, if your system is already registered or has a subscription that provides Certificate Server attached. Register the system to the Red Hat subscription management service. You can use the --auto-attach option to automatically apply an available subscription for the operating system. List the available subscriptions and note the pool ID providing the Red Hat Certificate System. For example: In case you have a lot of subscriptions, the output of the command can be very long. You can optionally redirect the output to a file: Attach the Certificate System subscription to the system using the pool ID from the step: Enable the Certificate System repository: Enable the Certificate System module stream: Installing the required packages is described in the Chapter 7, Installing and Configuring Certificate System chapter. Note For compliance, only enable Red Hat approved repositories. Only Red Hat approved repositories can be enabled through subscription-manager utility.

Commands:
subscription-manager register --auto-attach Username: admin@example.com Password: The system has been registered with id: 566629db-a4ec-43e1-aa02-9cbaa6177c3f Installed Product Current Status: Product Name: Red Hat Enterprise Linux Server Status: Subscribed
subscription-manager list --available --all Subscription Name: Red Hat Enterprise Linux Developer Suite Provides: Red Hat Certificate System Pool ID: 7aba89677a6a38fc0bba7dac673f7993 Available: 1
subscription-manager list --available --all > /root/subscriptions.txt
subscription-manager attach --pool= 7aba89677a6a38fc0bba7dac673f7993 Successfully attached a subscription for: Red Hat Enterprise Linux Developer Suite
subscription-manager repos --enable certsys-10-for-rhel-8-x86_64-eus-rpms Repository 'certsys-10-for-rhel-8-x86_64-eus-rpms' is enabled for this system.
dnf module enable redhat-pki
Chapter 35. KafkaClusterTemplate schema reference Used in: KafkaClusterSpec Property Description statefulset The statefulset property has been deprecated. Support for StatefulSets was removed in AMQ Streams 2.5. This property is ignored. Template for Kafka StatefulSet . StatefulSetTemplate pod Template for Kafka Pods . PodTemplate bootstrapService Template for Kafka bootstrap Service . InternalServiceTemplate brokersService Template for Kafka broker Service . InternalServiceTemplate externalBootstrapService Template for Kafka external bootstrap Service . ResourceTemplate perPodService Template for Kafka per-pod Services used for access from outside of OpenShift. ResourceTemplate externalBootstrapRoute Template for Kafka external bootstrap Route . ResourceTemplate perPodRoute Template for Kafka per-pod Routes used for access from outside of OpenShift. ResourceTemplate externalBootstrapIngress Template for Kafka external bootstrap Ingress . ResourceTemplate perPodIngress Template for Kafka per-pod Ingress used for access from outside of OpenShift. ResourceTemplate persistentVolumeClaim Template for all Kafka PersistentVolumeClaims . ResourceTemplate podDisruptionBudget Template for Kafka PodDisruptionBudget . PodDisruptionBudgetTemplate kafkaContainer Template for the Kafka broker container. ContainerTemplate initContainer Template for the Kafka init container. ContainerTemplate clusterCaCert Template for Secret with Kafka Cluster certificate public key. ResourceTemplate serviceAccount Template for the Kafka service account. ResourceTemplate jmxSecret Template for Secret of the Kafka Cluster JMX authentication. ResourceTemplate clusterRoleBinding Template for the Kafka ClusterRoleBinding. ResourceTemplate podSet Template for Kafka StrimziPodSet resource. ResourceTemplate

Commands:
8.4.4. Deactivating KSM Kernel same-page merging (KSM) has a performance overhead which may be too large for certain environments or host systems. KSM may also introduce side channels that could be potentially used to leak information across guests. If this is a concern, KSM can be disabled on per-guest basis. KSM can be deactivated by stopping the ksmtuned and the ksm services. However, this action does not persist after restarting. To deactivate KSM, run the following in a terminal as root: Stopping the ksmtuned and the ksm deactivates KSM, but this action does not persist after restarting. Persistently deactivate KSM with the systemctl commands: When KSM is disabled, any memory pages that were shared prior to deactivating KSM are still shared. To delete all of the PageKSM in the system, use the following command: After this is performed, the khugepaged daemon can rebuild transparent hugepages on the KVM guest physical memory. Using # echo 0 >/sys/kernel/mm/ksm/run stops KSM, but does not unshare all the previously created KSM pages (this is the same as the # systemctl stop ksmtuned command).

Commands:
systemctl stop ksmtuned Stopping ksmtuned: [ OK ] systemctl stop ksm Stopping ksm: [ OK ]
systemctl disable ksm systemctl disable ksmtuned
echo 2 >/sys/kernel/mm/ksm/run
probe::ipmib.InReceives Name probe::ipmib.InReceives - Count an arriving packet Synopsis ipmib.InReceives Values skb pointer to the struct sk_buff being acted on op value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function ipmib_filter_key . If the packet passes the filter is is counted in the global InReceives (equivalent to SNMP's MIB IPSTATS_MIB_INRECEIVES)

Commands:
13.2. Certificate Management in Firefox To manage certificates in Firefox, open the Certificate Manager . In Mozilla Firefox, open the Firefox menu and click Preferences . Figure 13.2. Firefox Preferences Open the Advanced section and choose the Certificates tab. Figure 13.3. Certificates Tab in Firefox Click View Certificates to open the Certificate Manager . To import a CA certificate: Download and save the CA certificate to your computer. In the Certificate Manager , choose the Authorities tab and click Import . Figure 13.4. Importing the CA Certificate in Firefox Select the downloaded CA certificate. To set the certificate trust relationships: In the Certificate Manager , under the Authorities tab, select the appropriate certificate and click Edit Trust . Edit the certificate trust settings. Figure 13.5. Editing the Certificate Trust Settings in Firefox To use a personal certificate for authentication: In the Certificate Manager , under the Your Certificates tab, click Import . Figure 13.6. Importing a Personal Certificate for Authentication in Firefox Select the required certificate from your computer.

Commands:
D.3. Manually Setting Up Encrypted Communication for VDSM You can manually set up encrypted communication for VDSM with the Manager and with other VDSM instances. Only hosts in clusters with cluster level 3.6, 4.0, and 4.1 require manual configuration. Hosts in clusters with level 4.2 are automatically reconfigured for strong encryption during host reinstallation. Note RHVH 3.6, 4.0, and 4.1 hosts do not support strong encryption. RHVH 4.2 and RHEL host do support it. If you have 3.6, 4.0, or 4.1 clusters with RHVH 4.2 hosts, you can use strong encryption. Procedure Click Compute Hosts and select the host. Click Management Maintenance to open the Maintenance Host(s) confirmation window. Click OK to initiate maintenance mode. On the host, create /etc/vdsm/vdsm.conf.d/99-custom-ciphers.conf with the following setting: See OpenSSL Cipher Strings for more information. Restart VDSM: Click Compute Hosts and select the host. Click Management Activate to reactivate the host.

Commands:
[vars] ssl_ciphers = HIGH
systemctl restart vdsm
8.145. perl-DateTime 8.145.1. RHBA-2013:1566 - perl-DateTime bug fix update Updated perl-DateTime packages that fix one bug are now available for Red Hat Enterprise Linux 6. DateTime is a class for the representation of date/time combinations, and is part of the Perl DateTime project. Bug Fix BZ# 978360 Previously, DateTime::Duration did not recognize the leap to 2012-07-01, which led to inaccurate computing time duration through the 2012-06-30T23:59:60 second. To fix this bug, a leap second appended in the end of 2012-06-30 has been added to perl-DateTime leap second database. Time arithmetic using Perl modules DateTime and DateTime::Duration now recognizes the leap from 2012-06-30 second correctly. Users of perl-DateTime are advised to upgrade to these updated packages, which fix this bug.

Commands:
probe::linuxmib.ListenDrops Name probe::linuxmib.ListenDrops - Count of times conn request that were dropped Synopsis linuxmib.ListenDrops Values sk Pointer to the struct sock being acted on op Value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function linuxmib_filter_key . If the packet passes the filter is is counted in the global ListenDrops (equivalent to SNMP's MIB LINUX_MIB_LISTENDROPS)

Commands:
Appendix A. Revision History Revision History Revision 1.0-1.33.402 Fri Oct 25 2013 Rudiger Landmann Rebuild with Publican 4.0.0 Revision 1.0-1.33 July 24 2012 Ruediger Landmann Rebuild for Publican 3.0 Revision 1.0-1 Thu Sep 18 2008 Don Domingo migrated to new automated build system

Commands: