mtpti5iD/redhat-docs_dataset huggingface dataset:
7.117. libldb 7.117.1. RHBA-2013:0372 - libldb bug fix and enhancement update Updated libldb packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libldb packages provide an extensible library that implements an LDAP-like API to access remote LDAP servers, or use local TDB databases. Note The libldb packages have been upgraded to upstream version 1.1.13, which provides a number of bug fixes and enhancements over the version. One of the most significant changes is that the source code of libldb is no longer a part of the samba4 packages but has been extracted to a separate SRPM package. This resolves the problem caused by recent changes in the Samba build system, which made the libldb library impossible to build as a shared library from the Samba tarball. (BZ#859229) Bug Fix BZ#873422 Recent changes in the Samba compiling script caused libldb to expose internal functions and symbols in the public interface. This could lead to various linking and building problems if these internal symbols were used directly out of the libldb code. This update corrects the compiling script so that internal symbols of libldb are no longer exported and visible in the libldb public interface. All users of libldb are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
2.4. Documenting the Site Survey Because of the complexity of data design, document the results of the site surveys. Each step of the site survey can use simple tables to track data. Consider building a supplier table that outlines the decisions and outstanding concerns. A good tip is to use a spreadsheet so that the table's contents can easily be sorted and searched. Table 2.4, "Example: Tabulating Data Ownership and Access" identifies data ownership and data access for each piece of data identified by the site survey. Table 2.4. Example: Tabulating Data Ownership and Access Data Name Owner Supplier Server/Application Self Read/Write Global Read HR Writable IS Writable Employee name HR PeopleSoft Read-only Yes (anonymous) Yes Yes User password IS Directory US-1 Read/Write No No Yes Home phone number HR PeopleSoft Read/Write No Yes No Employee location IS Directory US-1 Read-only Yes (must log in) No Yes Office phone number Facilities Phone switch Read-only Yes (anonymous) No No Each row in the table shows what kind of information is being assessed, what departments have an interest in it, and how the information is used and accessed. For example, on the first row, the employee names data have the following management considerations: Owner . Human Resources owns this information and therefore is responsible for updating and changing it. Supplier Server/Application . The PeopleSoft application manages employee name information. Self Read/Write . A person can read his own name but not write (or change) it. Global Read . Employee names can be read anonymously by everyone with access to the directory. HR Writable . Members of the human resources group can change, add, and delete employee names in the directory. IS Writable . Members of the information services group can change, add, and delete employee names in the directory.

Commands:
7.44. edac-utils 7.44.1. RHBA-2015:1430 - edac-utils bug fix update Updated edac-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The edac-utils packages contain Error Detection And Correction (EDAC), the current set of drivers in the Linux kernel that handles detection of ECC errors from memory controllers for most chipsets on the 32-bit and 64-bit architectures. The user-space component consists of an init script which ensures that EDAC drivers and Dual Inline Memory Module (DIMM) labels are loaded at system startup, as well as a library and utility for reporting current error counts from the EDAC sysfs files. Bug Fix BZ# 1200884 Previously, the libsysfs packages were not listed as a dependency for the edac-utils packages. As a consequence, on systems where the libsysfs packages were not installed independently, the edac-utils packages were not fully functional due to the lack of libraries provided by libsysfs. This update adds libsysfs to the list of dependencies for edac-utils. As a result, libsysfs can be automatically installed together with edac-utils, thus providing all the libsysfs libraries necessary for edac-utils to work properly on all systems. Users of edac-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 15. Logging in to the subscriptions service You access the subscriptions service from the Hybrid Cloud Console after logging in to your Red Hat Customer Portal login. Procedure In a browser window, go to console.redhat.com . If prompted, enter your Red Hat Customer Portal login credentials. In the Hybrid Cloud Console dashboard, click Services and then click Subscriptions and Spend in the navigation panel. On the Subscriptions and Spend page, click the Overview option for Subscription Services. In the navigation panel of the Subscription Services page, expand Subscriptions Usage. Click one of the Red Hat platform options, Red Hat Enterprise Linux , OpenShift , or Ansible , depending on the type of product usage that you want to view. Note If more than one product is generating usage for the subscriptions service, the platform page opens to a default view with a specific product variant or architecture in the Variant filter. Select another option in the Variant filter to view information about other architectures or product variants. If the subscriptions service is activated and the initial data processing is complete, the subscriptions service opens and displays data on the graph. You can begin using the subscriptions service to view data about subscription usage and capacity for the account. Note If the subscriptions service opens but displays an empty graph, then the subscriptions service is activated but the initial data processing is not complete. Try accessing the subscriptions service later, typically the day.

Commands:
7.178. perl-IPC-Run 7.178.1. RHBA-2012:1336 - perl-IPC-Run bug fix update Updated perl-IPC-Run packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl-IPC-Run packages provide a mechanism for Perl scripts to interact with child processes. Bug Fix BZ# 856840 Prior to this update, the IO::Pty Perl module was not loaded when using the command "IPC::Run::harness" with the ">pty>" argument if the perl-IO-Tty package was not installed. As a consequence, the Perl code failed. This update adds a perl-IO-Tty dependency to the perl-IPC-Run packages. All users of perl-IPC-Run are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. RHEL image builder description To deploy a system, create a system image. To create RHEL system images, use the RHEL image builder tool. You can use RHEL image builder to create customized system images of RHEL, including system images prepared for deployment on cloud platforms. RHEL image builder automatically handles the setup details for each output type and is therefore easier to use and faster to work with than manual methods of image creation. You can access the RHEL image builder functionalities by using the command line in the composer-cli tool, or the graphical user interface in the RHEL web console. 1.1. RHEL image builder terminology RHEL image builder uses the following concepts: Blueprint A blueprint is a description of a customized system image. It lists the packages and customizations that will be part of the system. You can edit blueprints with customizations and save them as a particular version. When you create a system image from a blueprint, the image is associated with the blueprint in the RHEL image builder interface. Create blueprints in the TOML format. Compose Composes are individual builds of a system image, based on a specific version of a particular blueprint. Compose as a term refers to the system image, the logs from its creation, inputs, metadata, and the process itself. Customizations Customizations are specifications for the image that are not packages. This includes users, groups, and SSH keys. 1.2. RHEL image builder output formats RHEL image builder can create images in multiple output formats shown in the following table. Table 1.1. RHEL image builder output formats Description CLI name File extension QEMU Image qcow2 .qcow2 Disk Archive tar .tar Amazon Web Services raw .raw Microsoft Azure vhd .vhd Google Cloud Platform gce .tar.gz VMware vSphere vmdk .vmdk VMware vSphere ova .ova Openstack openstack .qcow2 RHEL for Edge Commit edge-commit .tar RHEL for Edge Container edge-container .tar RHEL for Edge Installer edge-installer .iso RHEL for Edge Raw Image edge-raw-image .raw.xz RHEL for Edge Simplified Installer edge-simplified-installer .iso RHEL for Edge AMI edge-ami .ami RHEL for Edge VMDK edge-vsphere .vmdk RHEL Installer image-installer .iso Oracle Cloud Infrastructure .oci .qcow2 To check the supported types, run the command: 1.3. Supported architectures for image builds RHEL image builder supports building images for the following architectures: AMD and Intel 64-bit ( x86_64 ) ARM64 ( aarch64 ) IBM Z ( s390x ) IBM POWER systems However, RHEL image builder does not support multi-architecture builds. It only builds images of the same system architecture that it is running on. For example, if RHEL image builder is running on an x86_64 system, it can only build images for the x86_64 architecture. 1.4. Additional resources RHEL image builder additional documentation index

Commands:
composer-cli compose types
Chapter 73. KafkaStatus schema reference Used in: Kafka Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. listeners ListenerStatus array Addresses of the internal and external listeners. kafkaNodePools UsedNodePoolStatus array List of the KafkaNodePools used by this Kafka cluster. registeredNodeIds integer array Registered node IDs used by this Kafka cluster. This field is used for internal purposes only and will be removed in the future. clusterId string Kafka cluster Id. operatorLastSuccessfulVersion string The version of the Streams for Apache Kafka Cluster Operator which performed the last successful reconciliation. kafkaVersion string The version of Kafka currently deployed in the cluster. kafkaMetadataVersion string The KRaft metadata.version currently used by the Kafka cluster. kafkaMetadataState string (one of [PreKRaft, ZooKeeper, KRaftMigration, KRaftDualWriting, KRaftPostMigration, KRaft]) Defines where cluster metadata are stored. Possible values are: ZooKeeper if the metadata are stored in ZooKeeper; KRaftMigration if the controllers are connected to ZooKeeper, brokers are being rolled with Zookeeper migration enabled and connection information to controllers, and the metadata migration process is running; KRaftDualWriting if the metadata migration process finished and the cluster is in dual-write mode; KRaftPostMigration if the brokers are fully KRaft-based but controllers being rolled to disconnect from ZooKeeper; PreKRaft if brokers and controller are fully KRaft-based, metadata are stored in KRaft, but ZooKeeper must be deleted; KRaft if the metadata are stored in KRaft. autoRebalance KafkaAutoRebalanceStatus The status of an auto-rebalancing triggered by a cluster scaling request.

Commands:
Chapter 12. Managing Red Hat Gluster Storage Logs The log management framework generates log messages for each of the administrative functionalities and the components to increase the user-serviceability aspect of Red Hat Gluster Storage Server. Logs are generated to track the event changes in the system. The feature makes the retrieval, rollover, and archival of log files easier and helps in troubleshooting errors that are user-resolvable. The Red Hat Gluster Storage Component logs are rotated on a weekly basis. Administrators can rotate a log file in a volume, as needed. When a log file is rotated, the contents of the current log file are moved to log-file-name.epoch-time-stamp .The components for which the log messages are generated with message-ids are glusterFS Management Service, Distributed Hash Table (DHT), and Automatic File Replication (AFR). 12.1. Log Rotation Log files are rotated on a weekly basis and the log files are zipped in the gzip format on a fortnightly basis. When the content of the log file is rotated, the current log file is moved to log-file- name.epoch-time-stamp. The archival of the log files is defined in the configuration file. As a policy, log file content worth 52 weeks is retained in the Red Hat Gluster Storage Server.

Commands:
32.6. Pre-installation Script You can add commands to run on the system immediately after the ks.cfg has been parsed. This section must be placed towards the end of the kickstart file, after the kickstart commands described in Section 32.4, "Kickstart Options" , and must start with the %pre command and end with the %end command. If your kickstart file also includes a %post section, the order of the %pre and %post sections does not matter. See Section 32.8, "Kickstart Examples" for example configuration files. Note The pre-installation script section of kickstart cannot manage multiple install trees or source media. This information must be included for each created ks.cfg file, as the pre-installation script occurs during the second stage of the installation process. You can access the network in the %pre section; however, name service has not been configured at this point, so only IP addresses work. Only the most commonly used commands are available in the pre-installation environment: arping , awk , basename , bash , bunzip2 , bzcat , cat , chattr , chgrp , chmod , chown , chroot , chvt , clear , cp , cpio , cut , date , dd , df , dirname , dmesg , du , e2fsck , e2label , echo , egrep , eject , env , expr , false , fdisk , fgrep , find , fsck , fsck.ext2 , fsck.ext3 , ftp , grep , gunzip , gzip , hdparm , head , hostname , hwclock , ifconfig , insmod , ip , ipcalc , kill , killall , less , ln , load_policy , login , losetup , ls , lsattr , lsmod , lvm , md5sum , mkdir , mke2fs , mkfs.ext2 , mkfs.ext3 , mknod , mkswap , mktemp , modprobe , more , mount , mt , mv , nslookup , openvt , pidof , ping , ps , pwd , readlink , rm , rmdir , rmmod , route , rpm , sed , sh , sha1sum , sleep , sort , swapoff , swapon , sync , tail , tar , tee , telnet , top , touch , true , tune2fs , umount , uniq , vconfig , vi , wc , wget , wipefs , xargs , zcat . Note The pre-install script is not run in the change root environment. --interpreter /usr/bin/python Allows you to specify a different scripting language, such as Python. Replace /usr/bin/python with the scripting language of your choice.

Commands:
B.3. How to Set Up Red Hat Virtualization Manager to Use FCoE You can configure Fibre Channel over Ethernet (FCoE) properties for host network interface cards from the Administration Portal. The fcoe key is not available by default and needs to be added to the Manager using the engine configuration tool. You can check whether fcoe has already been enabled by running the following command: You also need to install the required VDSM hook package on the hosts. Depending on the FCoE card on the hosts, special configuration may also be needed; see Configuring a Fibre Channel over Ethernet Interface in the Red Hat Enterprise Linux Storage Administration Guide . Adding the fcoe Key to the Manager On the Manager, run the following command to add the key: Restart the ovirt-engine service: Install the VDSM hook package on each of the Red Hat Enterprise Linux hosts on which you want to configure FCoE properties. The package is available by default on Red Hat Virtualization Host (RHVH). The fcoe key is now available in the Administration Portal. See Section 9.4.2, "Editing Host Network Interfaces and Assigning Logical Networks to Hosts" to apply FCoE properties to logical networks.

Commands:
engine-config -g UserDefinedNetworkCustomProperties
engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*USD'
systemctl restart ovirt-engine.service
yum install vdsm-hook-fcoe
3.3. CPU Monitors cpupower features a selection of monitors that provide idle and sleep state statistics and frequency information and report on processor topology. Some monitors are processor-specific, while others are compatible with any processor. Refer to the cpupower-monitor man page for details on what each monitor measures and which systems they are compatible with. Use the following options with the cpupower monitor command: -l - list all monitors available on your system. -m <monitor1> , <monitor2> - display specific monitors. Their identifiers can be found by running -l . command - display the idle statistics and CPU demands of a specific command.

Commands:
Chapter 42. ContainerTemplate schema reference Used in: CruiseControlTemplate , EntityOperatorTemplate , JmxTransTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , KafkaExporterTemplate , KafkaMirrorMakerTemplate , KafkaNodePoolTemplate , ZookeeperClusterTemplate Full list of ContainerTemplate schema properties You can set custom security context and environment variables for a container. The environment variables are defined under the env property as a list of objects with name and value fields. The following example shows two custom environment variables and a custom security context set for the Kafka broker containers: # ... template: kafkaContainer: env: - name: EXAMPLE_ENV_1 value: example.env.one - name: EXAMPLE_ENV_2 value: example.env.two securityContext: runAsUser: 2000 # ... Environment variables prefixed with KAFKA_ are internal to Streams for Apache Kafka and should be avoided. If you set a custom environment variable that is already in use by Streams for Apache Kafka, it is ignored and a warning is recorded in the log. 42.1. ContainerTemplate schema properties Property Property type Description env ContainerEnvVar array Environment variables which should be applied to the container. securityContext SecurityContext Security context for the container.

Commands:
template: kafkaContainer: env: - name: EXAMPLE_ENV_1 value: example.env.one - name: EXAMPLE_ENV_2 value: example.env.two securityContext: runAsUser: 2000
4.7. Red Hat Virtualization 4.3 Batch Update 6 (ovirt-4.3.9) 4.7.1. Bug Fix These bugs were fixed in this release of Red Hat Virtualization: BZ# 1752522 Previously, when upgrading RHV version 4.2 to 4.3 using Satellite, the upgrade failed with a UnicodeEncodeError. The current release fixes this issue. BZ# 1792874 Partial cleanups are not supported. Previously, when the user ran engine-cleanup, it asked whether to remove everything. If the user replied 'No' and selected specific components to remove, the result was a broken system. The current release fixes this issue by eliminating the question. When you run engine-cleanup, the only option is to remove everything. BZ# 1795726 Before this update, when migrating a virtual machine, information about the running guest agent wasn't always passed to the destination host, resulting in an after_migration life cycle event not being sent to the virtual machine on the destination host. This update fixes the issue, and the after_migration notification should work as expected. BZ# 1796967 The Red Hat Virtualization Host could not be deployed successfully on systems with an AMD Epyc CPU. In this release, Red Hat Virtualization Host deployment is successful. BZ# 1808038 In RHV 4.1, the default console of the self-hosted engine virtual machine is set to VGA. Previously, after upgrading from RHV version 4.1 to 4.3, these graphical console settings were locked and trying to change them produced an error message. The current release fixes this issue by setting the default display to VNC during the upgrade to 4.3. This fix enables you to change the graphical console setting for the hosted engine virtual machine. 4.7.2. Enhancements This release of Red Hat Virtualization features the following enhancements: BZ# 1698870 A new Red Hat knowledge base article is available at: https://access.redhat.com/articles/4921101 BZ# 1797496 The current release adds support for Red Hat CoreOS (RHCOS), a single-purpose container operating system. This support enables you to create virtual machines that run RHCOS. These virtual machines are also backward compatible with RHV 4.3 clusters. BZ# 1804117 Starting with this release, it is now possible to install Metrics Store on a disconnected system using Satellite. BZ# 1809470 The current version of OVN, ovn2.11-2.11.1-33, runs as a dedicated user. The current release of RHV includes this version of OVN and adjusts the secret key file permissions to accommodate the dedicated user. These secret keys are required for encrypted OVN communication. 4.7.3. Known Issues These known issues exist in Red Hat Virtualization at this time: BZ# 1804095 The Red Hat Virtualization engine-setup asks for the location of the Data Warehouse database after the Data Warehouse was migrated to a standalone server. Workaround: Manually set two of the Data Warehouse setup parameters in the configuration file to False.

Commands:
12.8.2. Creating a Storage Pool Using the vHBA It is recommended to define a libvirt storage pool based on the vHBA in order to preserve the vHBA configuration. Using a storage pool has two primary advantages: the libvirt code can easily find the LUN's path using the virsh command output, and virtual machine migration requires only defining and starting a storage pool with the same vHBA name on the target machine. To do this, the vHBA LUN, libvirt storage pool and volume name must be specified in the virtual machine's XML configuration. Refer to Section 12.8.3, "Configuring the Virtual Machine to Use a vHBA LUN" for an example. Create a SCSI storage pool To create a vHBA configuration, first create a libvirt 'scsi' storage pool XML file based on the vHBA using the format below. Note Ensure you use the vHBA created in Procedure 12.6, "Creating a vHBA" as the host name, modifying the vHBA name scsi_hostN to hostN for the storage pool configuration. In this example, the vHBA is named scsi_host5 , which is specified as <adapter name='host5'/> in a Red Hat Enterprise Linux 6 libvirt storage pool. It is recommended to use a stable location for the <path> value, such as one of the /dev/disk/by-{path|id|uuid|label} locations on your system. More information on <path> and the elements within <target> can be found at http://libvirt.org/formatstorage.html . In this example, the 'scsi' storage pool is named vhbapool_host3.xml : <pool type='scsi'> <name>vhbapool_host3</name> <uuid>e9392370-2917-565e-692b-d057f46512d6</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <adapter name='host5'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> Define the pool To define the storage pool (named vhbapool_host3 in this example), use the virsh pool-define command: Start the pool Start the storage pool with the following command: Enable autostart Finally, to ensure that subsequent host reboots will automatically define vHBAs for use in virtual machines, set the storage pool autostart feature (in this example, for a pool named vhbapool_host3 ):

Commands:
<pool type='scsi'> <name>vhbapool_host3</name> <uuid>e9392370-2917-565e-692b-d057f46512d6</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <adapter name='host5'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool>
virsh pool-define vhbapool_host3.xml Pool vhbapool_host3 defined from vhbapool_host3.xml
virsh pool-start vhbapool_host3 Pool vhbapool_host3 started
virsh pool-autostart vhbapool_host3