mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Fixed issues The following sections list the issues fixed in AMQ Streams 1.6.x. Red Hat recommends that you upgrade to the latest patch release if you are using AMQ Streams 1.6.x with RHEL 7 and 8. For details of the issues fixed in: Kafka 2.6.3, refer to the Kafka 2.6.3 Release Notes Kafka 2.6.2, refer to the Kafka 2.6.2 Release Notes Kafka 2.6.1, refer to the Kafka 2.6.1 Release Notes Kafka 2.6.0, refer to the Kafka 2.6.0 Release Notes 5.1. Fixed issues for AMQ Streams 1.6.7 The AMQ Streams 1.6.7 patch release (Long Term Support) is now available. AMQ Streams 1.6.7 is the latest Long Term Support release for use with RHEL 7 and 8. For additional details about the issues resolved in AMQ Streams 1.6.7, see AMQ Streams 1.6.x Resolved Issues . Log4j vulnerabilities AMQ Streams includes log4j 1.2.17. The release fixes a number of log4j vulnerabilities. For more information on the vulnerabilities addressed in this release, see the following CVE articles: CVE-2022-23307 CVE-2022-23305 CVE-2022-23302 CVE-2021-4104 CVE-2020-9488 CVE-2019-17571 CVE-2017-5645 5.2. Fixed issues for AMQ Streams 1.6.6 For additional details about the issues resolved in AMQ Streams 1.6.6, see AMQ Streams 1.6.x Resolved Issues . Log4j2 vulnerabilities AMQ Streams includes log4j2 2.17.1. The release fixes a number of log4j2 vulnerabilities. For more information on the vulnerabilities addressed in this release, see the following CVE articles: CVE-2021-45046 CVE-2021-45105 CVE-2021-44832 CVE-2021-44228 5.3. Fixed issues for AMQ Streams 1.6.5 For additional details about the issues resolved in AMQ Streams 1.6.5, see AMQ Streams 1.6.x Resolved Issues . Log4j2 vulnerability The 1.6.5 release fixes a remote code execution vulnerability for AMQ Streams components that use log4j2. The vulnerability could allow a remote code execution on the server if the system logs a string value from an unauthorized source. This affects log4j versions between 2.0 and 2.14.1. For more information, see CVE-2021-44228 . 5.4. Fixed issues for AMQ Streams 1.6.4 For additional details about the issues resolved in AMQ Streams 1.6.4, see AMQ Streams 1.6.x Resolved Issues . 5.5. Fixed issues for AMQ Streams 1.6.0 Issue Number Description ENTMQST-2049 Kafka Bridge: Kafka consumer should be tracked with group-consumerid key ENTMQST-2084 Zookeeper version on the docs doesn't match with the version in AMQ Streams 1.5

Commands:
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 AMQ Streams for Apache Kafka entries in the 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-04-13 17:50:11 UTC

Commands:
13.2. XML representation of a Storage Connection Resource Example 13.1. An XML representation of a storage connection resource

Commands:
<storage_connections> <storage_connection href= "/ovirt-engine/api/storageconnections/608c5b96-9939-4331-96b5-197f28aa2e35" id="608c5b96-9939-4331-96b5-197f28aa2e35"> <address>domain.example.com</address> <type>nfs</type> <path>/var/lib/exports/iso</path> </storage_connection> <storage_connection href= "/ovirt-engine/api/storageconnections/2ebb3f78-8c22-4666-8df4-e4bb7fec6b3a" id="2ebb3f78-8c22-4666-8df4-e4bb7fec6b3a"> <address>domain.example.com</address> <type>posixfs</type> <path>/export/storagedata/username/data</path> <vfs_type>nfs</vfs_type> </storage_connection> </storage_connections>
Chapter 2. Red Hat Decision Manager components The product is made up of Business Central and KIE Server. Business Central is the graphical user interface where you create and manage business rules. You can install Business Central in a Red Hat JBoss EAP instance or on the Red Hat OpenShift Container Platform (OpenShift). Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server. KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. You can install KIE Server in a Red Hat JBoss EAP instance, in a Red Hat JBoss EAP cluster, on OpenShift, in an Oracle WebLogic server instance, in an IBM WebSphere Application Server instance, or as a part of Spring Boot application. You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). A KIE container is a specific version of a project. If KIE Server is managed, the Process Automation Manager controller manages the KIE Server configuration and you interact with the Process Automation Manager controller to create and maintain KIE containers. The Process Automation Manager controller is integrated with Business Central. If you install Business Central on Red Hat JBoss EAP, use the Execution Server page to create and maintain KIE containers. However, if you do not install Business Central, you can install the headless Process Automation Manager controller and use the REST API or the KIE Server Java Client API to interact with it. Red Hat build of OptaPlanner is integrated in Business Central and KIE Server. It is a lightweight, embeddable planning engine that optimizes planning problems. Red Hat build of OptaPlanner helps Java programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with efficient score calculations.

Commands:
Chapter 24. Extending a Stratis volume with additional block devices You can attach additional block devices to a Stratis pool to provide more storage capacity for Stratis file systems. You can do it manually or by using the web console. 24.1. Adding block devices to a Stratis pool You can add one or more block devices to a Stratis pool. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. The block devices that you are adding to the Stratis pool are not in use and not mounted. The block devices that you are adding to the Stratis pool are at least 1 GiB in size each. Procedure To add one or more block devices to the pool, use: Additional resources stratis(8) man page on your system 24.2. Adding a block device to a Stratis pool by using the web console You can use the web console to add a block device to an existing Stratis pool. You can also add caches as a block device. Prerequisites You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The stratisd service is running. A Stratis pool is created. The block devices on which you are creating a Stratis pool are not in use and are not mounted. Each block device on which you are creating a Stratis pool is at least 1 GB. Procedure Log in to the RHEL 9 web console. For details, see Logging in to the web console . Click Storage . In the Storage table, click the Stratis pool to which you want to add a block device. On the Stratis pool page, click Add block devices and select the Tier where you want to add a block device as data or cache. If you are adding the block device to a Stratis pool that is encrypted with a passphrase, enter the passphrase. Under Block devices , select the devices you want to add to the pool. Click Add .

Commands:
stratis pool add-data my-pool device-1 device-2 device-n
Chapter 14. Resolving common problems in RHUI 4 The following table lists known issues with Red Hat Update Infrastructure. If you encounter any of these issues, report the problem through Bugzilla. Table 14.1. Common problems in Red Hat Update Infrastructure Event Description of known issue Recommendation Installation and Configuration You experience communication issues between the RHUA and the CDSs. Verify the fully qualified domain name (FQDN) is set for the RHUA and CDS and is resolvable. Configure the HTTP proxy properly. Synchronization You cannot synchronize repositories with Red Hat. Verify the RHUI SKUs are in your account. Verify the proper content certificates are loaded to the RHUA. Look for temporary CDN issues. Look for any HTTP proxy in your environment. Red Hat Update Appliance/Content Delivery Network Communication The Red Hat Update Appliance is not communicating with the Content Delivery Network. Use the content certificate in /etc/pki/rhui/redhat (the .pem file) to test connectivity and access between the RHUA and the CDN. wget -O - --certificate /etc/pki/rhui/redhat/* --ca-certificate /etc/rhsm/ca/redhat-uep.pem https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/repodata/repomd.xml

Commands:
Chapter 19. Red Hat Enterprise Linux Atomic Host 7.5.4 19.1. Atomic Host OStree update : New Tree Version: 7.5.4 (hash: 519fd3f7efdfa5d0f6ecb0ab3cba84f95dbfa6b59e8a7176f3158adfaaa78334) Changes since Tree Version 7.5.3 (hash: 03d524a16c8d76897f097565ca7452c1a5e2541f8c2beab145adf622499c7c64) Updated packages : cockpit-ostree-176-1.el7 19.2. Extras Updated packages : dpdk-17.11-13.el7 cockpit-176-2.el7 atomic-1.22.1-25.git5a342e3.el7 podman-0.9.2-5.git37a2afe.el7_5 docker-1.13.1-75.git8633870.el7_5 runc-1.0.0-52.dev.git70ca035.el7_5 19.2.1. Container Images Updated : Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux Container Image (rhel7.5, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic openscap Container Image (rhel7/openscap) 19.3. New Features Buildah is now part of the default install With RHEL Atomic Host 7.5.4, Buildah is part of the default installation. You no longer need to install it using package layering.

Commands:
3.2. Managing Cluster Nodes The following sections describe the commands you use to manage cluster nodes, including commands to stop cluster services and to add and remove cluster nodes. 3.2.1. Stopping Cluster Services The following command stops cluster services on the specified node or nodes. As with the pcs cluster start , the --all option stops cluster services on all nodes and if you do not specify any nodes, cluster services are stopped on the local node only. You can force a stop of cluster services on the local node with the following command, which performs a kill -9 command.

Commands:
pcs cluster stop [--all] [ node ] [...]
pcs cluster kill
5.2. Generating SELinux Policy Modules: sepolicy generate In versions of Red Hat Enterprise Linux, the sepolgen or selinux-polgengui utilities were used for generating a SELinux policy. These tools have been merged to the sepolicy suite. In Red Hat Enterprise Linux 7, the sepolicy generate command is used to generate an initial SELinux policy module template. Unlike sepolgen , it is not necessary to run sepolicy generate as the root user. This utility also creates an RPM spec file, which can be used to build an RPM package that installs the policy package file ( NAME .pp ) and the interface file ( NAME .if ) to the correct location, provides installation of the SELinux policy into the kernel, and fixes the labeling. The setup script continues to install SELinux policy and sets up the labeling. In addition, a manual page based on the installed policy is generated using the sepolicy manpage command. [7] Finally, sepolicy generate builds and compiles the SELinux policy and the manual page into an RPM package, ready to be installed on other systems. When sepolicy generate is executed, the following files are produced: NAME .te - type enforcing file This file defines all the types and rules for a particular domain. NAME .if - interface file This file defines the default file context for the system. It takes the file types created in the NAME.te file and associates file paths to the types. Utilities, such as restorecon and rpm , use these paths to write labels. NAME _selinux.spec - RPM spec file This file is an RPM spec file that installs SELinux policy and sets up the labeling. This file also installs the interface file and a man page describing the policy. You can use the sepolicy manpage -d NAME command to generate the man page. NAME .sh - helper shell script This script helps to compile, install, and fix the labeling on the system. It also generates a man page based on the installed policy, compiles, and builds an RPM package suitable to be installed on other systems. If it is possible to generate an SELinux policy module, sepolicy generate prints out all generated paths from the source domain to the target domain. See the sepolicy-generate (8) manual page for further information about sepolicy generate . [7] See Section 5.4, "Generating Manual Pages: sepolicy manpage " for more information about sepolicy manpage .

Commands:
C.5. Common Post-Installation Tasks The following sections are about common post-installation tasks. C.5.1. Set a Randomly Generated Key as an Additional Way to Access an Encrypted Block Device The following sections are about generating keys and adding keys. C.5.1.1. Generate a Key This will generate a 256-bit key in the file USDHOME/keyfile . C.5.1.2. Add the Key to an Available Keyslot on the Encrypted Device

Commands:
dd if=/dev/urandom of=USDHOME/keyfile bs=32 count=1 chmod 600 USDHOME/keyfile
cryptsetup luksAddKey <device> ~/keyfile
Chapter 3. Types of instance storage The virtual storage that is available to an instance is defined by the flavor used to launch the instance. The following virtual storage resources can be associated with an instance: Instance disk Ephemeral storage Swap storage Persistent block storage volumes Config drive 3.1. Instance disk The instance disk created to store instance data depends on the boot source that you use to create the instance. The instance disk of an instance that you boot from an image is controlled by the Compute service and deleted when the instance is deleted. The instance disk of an instance that you boot from a volume is a persistent volume provided by the Block Storage service. 3.2. Instance ephemeral storage You can specify that an ephemeral disk is created for the instance by choosing a flavor that configures an ephemeral disk. This ephemeral storage is an empty additional disk that is available to an instance. This storage value is defined by the instance flavor. The default value is 0, meaning that no secondary ephemeral storage is created. The ephemeral disk appears in the same way as a plugged-in hard drive or thumb drive. It is available as a block device, which you can check using the lsblk command. You can mount it and use it however you normally use a block device. You cannot preserve or reference that disk beyond the instance it is attached to. Note Ephemeral storage data is not included in instance snapshots, and is not available on instances that are shelved and then unshelved. 3.3. Instance swap storage You can specify that a swap disk is created for the instance by choosing a flavor that configures a swap disk. This swap storage is an additional disk that is available to the instance for use as swap space for the running operating system. 3.4. Instance block storage A block storage volume is persistent storage that is available to an instance regardless of the state of the running instance. You can attach multiple block devices to an instance, one of which can be a bootable volume. Note When you use a block storage volume for your instance disk data, the block storage volume persists for any instance rebuilds, even when an instance is rebuilt with a new image that requests that a new volume is created. 3.5. Config drive You can attach a config drive to an instance when it boots. The config drive is presented to the instance as a read-only drive. The instance can mount this drive and read files from it. You can use the config drive as a source for cloud-init information. Config drives are useful when combined with cloud-init for server bootstrapping, and when you want to pass large files to your instances. For example, you can configure cloud-init to automatically mount the config drive and run the setup scripts during the initial instance boot. Config drives are created with the volume label of config-2 , and attached to the instance when it boots. The contents of any additional files passed to the config drive are added to the user_data file in the openstack/{version}/ directory of the config drive. cloud-init retrieves the user data from this file.

Commands:
Chapter 2. Major changes in version 1.8 Be aware of the following differences between Red Hat Hyperconverged Infrastructure for Virtualization 1.8 and versions: Changed behavior Red Hat Hyperconverged Infrastructure for Virtualization 1.8 and Red Hat Virtualization 4.4 are based on Red Hat Enterprise Linux 8. Read about the key differences in Red Hat Enterprise Linux 8 in Considerations in adopting RHEL 8 . Cluster upgrades now require at least 10 percent free space on gluster disks in order to reduce the risk of running out of space mid-upgrade. This is available post the upgrade to Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1783750 ) "Hosts" and "Additional Hosts" tabs in the Web Console have been combined into a new "Hosts" tab that shows information previously shown on both. ( BZ#1762804 ) Readcache and readcachesize options have been removed from VDO volumes, as they are not supported on Red Hat Enterprise Linux 8 based operating systems. ( BZ#1808081 ) The Quartz scheduler is replaced with the standard Java scheduler to match support with Red Hat Virtualization. ( BZ#1797487 ) Enhancements The Administrator Portal can now upgrade all hosts in a cluster with one click. This is available post the upgrade to Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1721366 ) At-rest encryption using Network-Bound Disk Encryption (NBDE) is now supported on new Red Hat Hyperconverged Infrastructure for Virtualization deployments. ( BZ#1821248 , BZ#1781184 ) Added support for IPv6 networking. Environments with both IPv4 and IPv6 addresses are not supported. ( BZ#1721383 ) New roles, playbooks, and inventory examples are available to simplify and automate the following tasks: Upgrading ( BZ#1500728 , BZ#1832654 ) Backing up and restoring configuration ( BZ#1850488 ) Replacing hosts ( BZ#1840123 ) Blacklisting multipath devices ( BZ#1807808 ) Creating the gluster logical network ( BZ#1832966 ) Deploying on IPv6 networks. ( BZ#1688217 ) Added an option to select IPv4 or IPv6 based deployment in the web console. ( BZ#1688798 ) fsync in the replication module now uses eager-lock functionality which improves the performance of small-block of size approximately equal to 4k write-heavy workloads by more than 50 percent on Red Hat Hyperconverged Infrastructure for Virtualization 1.8. ( BZ#1836164 ) The web console now supports blacklisting multipath devices. ( BZ#1814120 ) New fencing policies skip_fencing_if_gluster_bricks_up and skip_fencing_if_gluster_quorum_not_met are now added and enabled by default. ( BZ#1775552 ) Red Hat Hyperconverged Infrastructure for Virtualization now ensures that the "performance.strict-o-direct" option in Red Hat Gluster Storage is enabled before creating a storage domain. ( BZ#1807400 ) Red Hat Gluster Storage volume options can now be set for all volumes in the Administrator Portal by using "all" as the volume name. ( BZ#1775586 ) Read-only fields are no longer included in the web console user interface, making the interface simpler and easier to read. ( BZ#1814553 )

Commands:
Chapter 1. Red Hat OpenShift support for Windows Containers overview You can add Windows nodes either by creating a compute machine set or by specifying existing Bring-Your-Own-Host (BYOH) Window instances through a configuration map . Note Compute machine sets are not supported for bare metal or provider agnostic clusters. For workloads including both Linux and Windows, OpenShift Container Platform allows you to deploy Windows workloads running on Windows Server containers while also providing traditional Linux workloads hosted on Red Hat Enterprise Linux CoreOS (RHCOS) or Red Hat Enterprise Linux (RHEL). For more information, see getting started with Windows container workloads . You need the WMCO to run Windows workloads in your cluster. The WMCO orchestrates the process of deploying and managing Windows workloads on a cluster. For more information, see how to enable Windows container workloads . You can create a Windows MachineSet object to create infrastructure Windows machine sets and related machines so that you can move supported Windows workloads to the new Windows machines. You can create a Windows MachineSet object on multiple platforms. You can schedule Windows workloads to Windows compute nodes. You can perform Windows Machine Config Operator upgrades to ensure that your Windows nodes have the latest updates. You can remove a Windows node by deleting a specific machine. You can use Bring-Your-Own-Host (BYOH) Windows instances to repurpose Windows Server VMs and bring them to OpenShift Container Platform. BYOH Windows instances benefit users who are looking to mitigate major disruptions in the event that a Windows server goes offline. You can use BYOH Windows instances as nodes on OpenShift Container Platform 4.8 and later versions. You can disable Windows container workloads by performing the following: Uninstalling the Windows Machine Config Operator Deleting the Windows Machine Config Operator namespace

Commands:
8.5. Managing Organizational Units Administrators can use organizational units (OU) as a container for directory entries. For example, you can use OUs to separate user and group entries. To manage OUs in Directory Server, use the dsidm organizationalunit command. To create an OU, enter: To list the OUs in an entry, enter: To rename an OU, enter: To delete an OU, enter:

Commands:
dsidm -D "cn=Directory Manager" ldap://server.example.com -b " dc=example,dc=com " organizationalunit create --ou OU_name
dsidm -D "cn=Directory Manager" ldap://server.example.com -b " dc=example,dc=com " organizationalunit list People
dsidm -D "cn=Directory Manager" ldap://server.example.com -b " dc=example,dc=com " organizationalunit rename old_name new_name
dsidm -D "cn=Directory Manager" ldap://server.example.com -b " dc=example,dc=com " organizationalunit delete OU_name