mtpti5iD/redhat-docs_dataset huggingface dataset:
8.191. python-virtinst 8.191.1. RHBA-2014:1444 - python-virtinst bug fix and enhancement update Updated python-virtinst package that fixes several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The python-virtinst package contains several command-line utilities, including virt-install for building and installing new virtual machines, and virt-clone for cloning existing virtual machines. Bug Fixes BZ# 853386 Due to a bug in the python-virtinst package, the "virt-install --graphics spice" command did not create a spicevmc channel. This bug has been fixed and the aforementioned command now works as expected. BZ# 873545 Due to a bug in the python-virtinst package, the "sparse=false" parameter of the virt-install command was ignored and the newly crated storage was not fully allocated. This bug has been fixed and the "virt-install sparse=false" command now works correctly. BZ# 1000980 Prior to this update, when the allocation of a new lvm volume was set to 0 with the virt-install utility, no error message was returned. With this update, virt-install has been modified to display an error message in the aforementioned case. BZ# 1055225 The virt-manager utility failed to clone virtual machines (VMs) with fully allocated logical volumes. After clicking the Clone button in virt-manager GUI, the following message was displayed: Sparse logical volumes are not supported This bug has been fixed and VMs with fully allocated logical volumes can now be cloned successfully with virt-manager GUI. BZ# 1077232 When the virt-install command was executed with the "device=lun" option, it terminated with the following message: Unknown device type 'lun' This bug has been fixed, and lun device type is now recognized correctly by virt-install. BZ# 1085499 When selecting a PCI device to be assigned to a virtual machine, the virt-manager GUI did not display the domain of PCI devices. Consequently, it was impossible to assign a PCI device in any domain other than zero. This bug has been fixed and virt-manager now displays domains correctly in the described case. In addition, this update adds the following Enhancements BZ# 855740 This update adds support for the MacVTap device driver to the python-virtinst package. MacVTap, which facilitates virtualized bridged networking, can now be used when installing new virtual guest machines. BZ# 1001999 This update adds options for USB redirection to the python-virtinst package. BZ# 1011290 The list of operating system variants displayed by the "virt-install --os-variant list" command has been updated. BZ# 1017423 This update enables the startup_policy parameter for the --disk option of the virt-install command. This parameter allows to specify what to do with the disk if the source file is not accessible. It accepts the same parameters as the startupPolicy domain XML attribute. Users of python-virtinst are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 5. Cluster overview page The Cluster overview page shows the status of a Kafka cluster. Here, you can assess the readiness of Kafka brokers, identify any cluster errors or warnings, and gain insights into the cluster's health. At a glance, the page provides information on the number of topics and partitions within the cluster, along with their replication status. Explore cluster metrics through charts displaying used disk space, CPU utilization, and memory usage. Additionally, topic metrics offer a comprehensive view of total incoming and outgoing byte rates for all topics in the Kafka cluster. 5.1. Pausing reconciliation of clusters Pause cluster reconciliations from the Cluster overview page by following these steps. While paused, any changes to the cluster configuration using the Kafka custom resource are ignored until reconciliation is resumed. Procedure From the Streams for Apache Kafka Console, log in to the Kafka cluster that you want to connect to, then click Cluster overview and Pause reconciliation . Confirm the pause, after which the Cluster overview page shows a change of status warning that reconciliation is paused. Click Resume reconciliation to restart reconciliation. Note If the status change is not displayed after pausing reconciliation, try refreshing the page. 5.2. Accessing cluster connection details for client access When connecting a client to a Kafka cluster, retrieve the necessary connection details from the Cluster overview page by following these steps. Procedure From the Streams for Apache Kafka Console, log in to the Kafka cluster that you want to connect to, then click Cluster overview and Cluster connection details . Copy and add bootstrap address and connection properties to your Kafka client configuration to establish a connection with the Kafka cluster. Note Ensure that the authentication type used by the client matches the authentication type configured for the Kafka cluster.

Commands:
Chapter 4. Finding more information The following table includes deployment references for Red Hat OpenStack Platform (RHOSP) components. For additional RHOSP documentation, see Product Documentation for Red Hat OpenStack Platform 17.0 . Component Reference Red Hat Enterprise Linux Red Hat OpenStack Platform 17.0 is supported on Red Hat Enterprise Linux 8.4. For information about installing Red Hat Enterprise Linux, see Product Documentation for Red Hat Enterprise Linux 8 . Red Hat OpenStack Platform To install OpenStack components and their dependencies, use RHOSP director. Director uses a basic OpenStack undercloud to provision and manage the OpenStack nodes in the final overcloud. Be aware that you need one extra host machine for the installation of the undercloud, in addition to the environment necessary for the deployed overcloud. For more information, see the Director Installation and Usage guide. High Availability For the configuration of additional high availability components, for example, HAProxy, see the High Availability Deployment and Usage guide. For information about configuring live migration, see Migrating virtual machine instances between Compute nodes in the Configuring the Compute Service for Instance Creation guide. Load-balancing The OpenStack Load-balancing service (octavia) provides a Load Balancing-as-a-Service (LBaaS) version 2 implementation for RHOSP director installations. For more information, see the Using Octavia for Load Balancing-as-a-Service guide. Pacemaker Pacemaker is integrated into Red Hat Enterprise Linux as an add-on. To configure Red Hat Enterprise Linux for high availability, see the Configuring and managing high availability clusters guide.

Commands:
Chapter 10. Add hyperconverged hosts to Red Hat Virtualization Manager Follow this process to allow Red Hat Virtualization Manager to manage an existing hyperconverged host. Log in to the Administration Portal. Click Compute Hosts . Click New . The New Host window opens. On the General tab, specify the following details about your hyperconverged host. Host Cluster Name Hostname Password On the General tab, click the Advanced Parameters dropdown, and uncheck the Automatically configure host firewall checkbox. Click OK .

Commands:
7.22. certmonger 7.22.1. RHBA-2013:0320 - certmonger bug fix and enhancement update Updated certmonger packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The certmonger daemon monitors certificates which have been registered with it, and as a certificate's not-valid-after date approaches, the daemon can optionally attempt to obtain a fresh certificate from a supported CA. Note The certmonger packages have been upgraded to upstream version 0.61, which provides a number of bug fixes and enhancements over the version. (BZ#827611) Bug Fixes BZ# 810016 When certmonger was set up to not attempt to obtain a new certificate and the certificate's valid remaining time crossed a configured time to live (TTL) threshold, certmonger warned of a certificate's impending not-valid-after date. Certmonger then immediately logged the warning again, and continued to do so indefinitely, causing the /var/log/messages file to fill up with warnings. This bug has been fixed and certmonger returns a warning again only when another configured TTL threshold is crossed or the service is restarted. BZ#893611 When certmonger attempts to save a certificate to an NSS database, it necessarily opens that database for writing. Previously, if any other process, including any other certmonger tasks that could require access to that database, had the database open for writing, that database could become corrupted. This update backports changes from later versions of certmonger which change its behavior. Now, actions that could result in database modifications are only performed one at a time. All users of certmonger are advised to upgrade to these updated packages which fix these bugs and add these enhancements.

Commands:
5.3.16. Recreating a Volume Group Directory To recreate a volume group directory and logical volume special files, use the vgmknodes command. This command checks the LVM2 special files in the /dev directory that are needed for active logical volumes. It creates any special files that are missing removes unused ones. You can incorporate the vgmknodes command into the vgscan command by specifying the mknodes argument to the vgscan command.

Commands:
Chapter 2. Installing the Red Hat Quay Operator from the OperatorHub Use the following procedure to install the Red Hat Quay Operator from the OpenShift Container Platform OperatorHub. Procedure Using the OpenShift Container Platform console, select Operators OperatorHub . In the search box, type Red Hat Quay and select the official Red Hat Quay Operator provided by Red Hat. This directs you to the Installation page, which outlines the features, prerequisites, and deployment information. Select Install . This directs you to the Operator Installation page. The following choices are available for customizing the installation: Update Channel: Choose the update channel, for example, stable-3.7 for the latest release. Installation Mode: Choose All namespaces on the cluster if you want the Red Hat Quay Operator to be available cluster-wide. Choose A specific namespace on the cluster if you want it deployed only within a single namespace. It is recommended that you install the Red Hat Quay Operator cluster-wide. If you choose a single namespace, the monitoring component will not be available by default. Approval Strategy: Choose to approve either automatic or manual updates. Automatic update strategy is recommended. Select Install .

Commands:
Chapter 1. Supported upgrade paths Currently, it is possible to perform an in-place upgrade from RHEL 8 to the following target RHEL 9 minor versions: System configuration Source OS version Target OS version SAP HANA RHEL 8.8 RHEL 9.2 RHEL 8.10 RHEL 9.4 SAP NetWeaver and other SAP Applications RHEL 8.8 RHEL 9.2 RHEL 8.10 RHEL 9.4 SAP HANA is validated by SAP for RHEL minor versions that receive package updates for more than 6 months. SAP NetWeaver is validated by SAP for each major RHEL version. The supported in-place upgrade path for both are the same as described in the Upgrading from RHEL 8 to RHEL 9 document. The upgrade of systems hosting SAP HANA and other SAP applications are very similar. Certain deviations are described in Section 4. Upgrading an SAP NetWeaver system . For systems on which both SAP HANA and SAP NetWeaver are installed, the SAP HANA restrictions apply. Please refer to the Planning an upgrade to RHEL 9 chapter for more details. Note For cloud providers (AWS, Azure, and GCP), PAYG VMs on RHUI, and for both options, RHEL for SAP HA and US and RHEL for SAP Applications, there is a known bug in upgrading from 8.10 to 9.4 due to a RHUI client rpm name difference in 8.10 compared to releases. The upgrade is not possible at the moment, and there is no workaround. The upgrade from 8.8 to 9.2 is not impacted.

Commands:
10.3.5. Establishing a DSL Connection This section is intended for those installations which have a DSL card fitted within a host rather than the external combined DSL modem router combinations typical of private consumer or SOHO installations. Procedure 10.7. Adding a New DSL Connection You can configure a new DSL connection by opening the Network Connections window, clicking the Add button and selecting DSL from the Hardware section of the new connection list. Right-click on the NetworkManager applet icon in the Notification Area and click Edit Connections . The Network Connections window appears. Click the Add button. The Choose a Connection Type list appears. Select DSL and press the Create button. The Editing DSL Connection 1 window appears. Procedure 10.8. Editing an Existing DSL Connection You can configure an existing DSL connection by opening the Network Connections window and selecting the name of the connection from the list. Then click the Edit button. Right-click on the NetworkManager applet icon in the Notification Area and click Edit Connections . The Network Connections window appears. Select the connection you want to edit and click the Edit button. Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings Three settings in the Editing dialog are common to all connection types: Connection name - Enter a descriptive name for your network connection. This name will be used to list this connection in the DSL section of the Network Connections window. Connect automatically - Check this box if you want NetworkManager to auto-connect to this connection when it is available. See Section 10.2.3, "Connecting to a Network Automatically" for more information. Available to all users - Check this box to create a connection available to all users on the system. Changing this setting may require root privileges. See Section 10.2.4, "User and System Connections" for details. Configuring the DSL Tab Username Enter the user name used to authenticate with the service provider. Service Leave blank unless otherwise directed. Password Enter the password supplied by the service provider. Saving Your New (or Modified) Connection and Making Further Configurations Once you have finished editing your DSL connection, click the Apply button and NetworkManager will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the NetworkManager Notification Area applet. See Section 10.2.1, "Connecting to a Network" for information on using your new or altered connection. You can further configure an existing connection by selecting it in the Network Connections window and clicking Edit to return to the Editing dialog. Then, to configure: The MAC address and MTU settings, click the Wired tab and proceed to the section called "Configuring the Wired Tab" ; Point-to-point settings for the connection, click the PPP Settings tab and proceed to Section 10.3.9.3, "Configuring PPP (Point-to-Point) Settings" ; IPv4 settings for the connection, click the IPv4 Settings tab and proceed to Section 10.3.9.4, "Configuring IPv4 Settings" .

Commands:
Chapter 17. complete.adoc This chapter describes the commands under the complete.adoc command. 17.1. complete print bash completion command Usage: Table 17.1. Command arguments Value Summary -h, --help Show this help message and exit --name <command_name> Command name to support with command completion --shell <shell> Shell being used. use none for data only (default: bash)

Commands:
openstack complete [-h] [--name <command_name>] [--shell <shell>]
8.45. foomatic 8.45.1. RHBA-2013:1084 - foomatic bug fix update Updated foomatic packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Foomatic is a comprehensive, spooler-independent database of printers, printer drivers, and driver descriptions. The package also includes spooler-independent command line interfaces to manipulate queues and to print files and manipulate print jobs. foomatic-rip is a print filter written in C. Bug Fixes BZ# 661770 The foomatic package could not be rebuilt due to the RPM package spec file having incorrect locations for Perl files. The installation locations have been fixed and the package can now be rebuilt. BZ# 726385 Under certain circumstances, the foomatic-rip CUPS filter could fail, causing print jobs to pass raw data to the printer without being correctly filtered. This was caused by a missing parameter to a logging function. This programming error has been corrected and foomatic-rip now behaves correctly in the described scenario. Users of foomatic are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 8. Consumer groups page The Consumer groups page shows all the consumer groups associated with a Kafka cluster. For each consumer group, you can see its status, the overall consumer lag across all partitions, and the number of members. Click on associated topics to show the topic information available from the Topics page tabs . Consumer group status can be one of the following: Stable indicates normal functioning Rebalancing indicates ongoing adjustments to the consumer group's members. Empty suggests no active members. If in the empty state, consider adding members to the group. Check group members by clicking on a consumer group name. For more information on checking consumer group members, see Section 8.1, "Checking consumer group members" . 8.1. Checking consumer group members Check the members of a specific consumer group from the Consumer groups page. Procedure From the Streams for Apache Kafka Console, click the name of the Kafka cluster, then click Consumer groups . Click the name of the consumer group you want to check from the Consumer groups page. Click on the right arrow (>) to a member ID to see the topic partitions a member is associated with, as well as any possible consumer lag. For each group member, you see the unique (consumer) client ID assigned to the consumer within the consumer group, overall consumer lag, and the number of assigned partitions. Any consumer lag for a specific topic partition reflects the gap between the last message a consumer has picked up (committed offset position) and the latest message written by the producer (end offset position).

Commands:
Chapter 9. Enabling and disabling automatic rule updates for Insights By default, automatic collection rule updates are enabled for Insights. You can edit the client configuration file to disable them or re-enable them. 9.1. Disabling automatic rule updates for Insights You can disable the automatic collection rule updates for Red Hat Insights for Red Hat Enterprise Linux. If you do so, you risk using outdated rule definition files and not getting the most recent validation updates. Prerequisites Root-level access to your system. Automatic rule updates are enabled. Procedure Open the /etc/insights-client/insights-client.conf file with an editor. Locate the line that contains Remove the # and change True to False . Save and close the /etc/insights-client/insights-client.conf file. 9.2. Enabling automatic rule updates for Insights You can re-enable the automatic collection rule updates for Red Hat Insights for Red Hat Enterprise Linux, if you previously disabled updates. By default, automatic rule update is enabled. Prerequisites Root-level access to your system. Automatic rule collection is disabled. Procedure Open the /etc/insights-client/insights-client.conf file with an editor. Locate the line that contains Change False to True . Save and close the /etc/insights-client/insights-client.conf file.

Commands:
#auto_update=True
auto_update=False
auto_update=False
auto_update=True
3.11. Searching for Networks The following table describes all search options for networks. Table 3.7. Searching for Networks Property (of resource or resource-type) Type Description (Reference) Cluster_network. clusternetwork-prop Depends on property type The property of the cluster associated with the network. Host_Network. hostnetwork-prop Depends on property type The property of the host associated with the network. name String The human readable name that identifies the network. description String Keywords or text describing the network, optionally used when creating the network. vlanid Integer The VLAN ID of the network. stp String Whether Spanning Tree Protocol (STP) is enabled or disabled for the network. mtu Integer The maximum transmission unit for the logical network. vmnetwork String Whether the network is only used for virtual machine traffic. datacenter String The data center to which the network is attached. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Network: mtu > 1500 and vmnetwork = true This example returns a list of networks with a maximum transmission unit greater than 1500 bytes, and which are set up for use by only virtual machines.

Commands:
4.232. plymouth 4.232.1. RHBA-2011:1766 - plymouth bug fix update Updated plymouth packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Plymouth provides a graphical boot animation in place of the text messages that are normally displayed. Text messages are instead redirected to a log file for viewing after boot. Bug Fixes BZ# 719569 Previously, plymouth incorrectly parsed "console" parameters that were set to "tty0" on the kernel command line. When the user had connected the serial port from another machine and rebooted the system, the boot log was not redirected to the serial console and the user could not view it as a consequence. A patch has been applied to address the issue so that users can now view the output of the boot log. BZ# 741515 Previously, plymouth did not perform proper tty clean up on some consoles if more than one line contained the "console=" parameter. The terminal was locked as a consequence and the user was not able to log in from the serial console. With this update, plymouth is modified to correctly handle multiple lines containing "console=" and users are now able to log in as expected. All users of plymouth are advised to upgrade to these updated packages, which fix these bugs.

Commands:
6.4. Specifying the Location of a Driver Update Image File or a Driver Update Disk If the installer detects more than one possible device that could hold a driver update, it prompts you to select the correct device. If you are not sure which option represents the device on which the driver update is stored, try the various options in order until you find the correct one. Figure 6.7. Selecting a driver disk source If the device that you choose contains no suitable update media, the installer will prompt you to make another choice. If you made a driver update disk on CD, DVD, or USB flash drive, the installer now loads the driver update. However, if the device that you selected is a type of device that could contain more than one partition (whether the device currently has more than one partition or not), the installer might prompt you to select the partition that holds the driver update. Figure 6.8. Selecting a driver disk partition The installer prompts you to specify which file contains the driver update: Figure 6.9. Selecting an ISO image Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a CD or DVD. Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk). The installer might ask whether you would like to use additional driver updates. If you select Yes , you can load additional updates in turn. When you have no further driver updates to load, select No . If you stored the driver update on removable media, you can now safely eject or disconnect the disk or device. The installer no longer requires the driver update, and you can re-use the media for other purposes.

Commands: