mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Known Issues 4.1. Reboot requirement detection The reboot requirement detection is not reliable on RHEL 8.5 and later on platform ppc64le. A failed reboot requirement detection can lead to unnecessary reboots at the end of a playbook which calls the preconfiguration roles. Role parameters are available for avoiding reboots, and playbooks can be extended to unconditionally reboot a system. See bug 2166444 for more information. 4.2. Extended check (Assert) function Be careful when using the extended check (=assert) function of the preconfigure roles. The preconfigure roles can run in an assert mode, in which case they do not modify managed nodes but report the compliance of a node with the applicable SAP notes. When using the same control node also for modifying the system configuration, by running the preconfigure roles in normal mode, extra caution needs to be applied to ensure that a "normal" playbook is not accidentally used for checking the system configuration. It is strongly recommended to only run the roles on production systems after testing them on test and QA systems first. 4.3. DNS name resolution Role sap_general_preconfigure fails if the DNS domain is not set on the managed node. In case there is no DNS domain set on the managed node, which is typically the case on cloud systems, the role sap_general_preconfigure will fail in task Verify that the DNS domain is set . To avoid this, set the role variable sap_domain in the vars section of your playbook, in an inventory file for the managed node or run the ansible-playbook command with parameter -e "sap_domain=example.com" (replace example.com by your own DNS domain name).

Commands:
3.4. Setting Up Multipathing in the initramfs File System You can set up multipathing in the initramfs file system. After configuring multipath, you can rebuild the initramfs file system with the multipath configuration files by executing the dracut command with the following options: If you run multipath from the initramfs file system and you make any changes to the multipath configuration files, you must rebuild the initramfs file system for the changes to take effect.

Commands:
dracut --force --add multipath --include /etc/multipath /etc/multipath
Chapter 4. Btrfs The B-tree file system ( Btrfs ) is a local file system that aims to provide better performance and scalability. Btrfs was introduced in Red Hat Enterprise Linux 6 as a Technology Preview, available on AMD64 and Intel 64 architectures. The Btrfs Technology Preview ended as of Red Hat Enterprise Linux 6.6 and will not be updated in the future. Btrfs will be included in future releases of Red Hat Enterprise Linux 6, but will not be supported in any way. Btrfs Features Several utilities are built in to Btrfs to provide ease of administration for system administrators. These include: Built-in System Rollback File system snapshots make it possible to roll a system back to a prior, known-good state if something goes wrong. Built-in Compression This makes saving space easier. Checksum Functionality This improves error detection. Specific features include integrated LVM operations, such as: dynamic, online addition or removal of new storage devices internal support for RAID across the component devices the ability to use different RAID levels for meta or user data full checksum functionality for all meta and user data.

Commands:
5.10. Migration The Red Hat Virtualization Manager uses migration to enforce load balancing policies for a cluster. Virtual machine migration takes place according to the load balancing policy for a cluster and current demands on hosts within a cluster. Migration can also be configured to automatically occur when a host is fenced or moved to maintenance mode. The Red Hat Virtualization Manager first migrates virtual machines with the lowest CPU utilization. This is calculated as a percentage, and does not take into account RAM usage or I/O operations, except as I/O operations affect CPU utilization. If there are more than one virtual machines with the same CPU usage, the one that will be migrated first is the first virtual machine returned by the database query run by the Red Hat Virtualization Manager to determine virtual machine CPU usage. Virtual machine migration has the following limitations by default: A bandwidth limit of 52 MiBps is imposed on each virtual machine migration. A migration will time out after 64 seconds per GB of virtual machine memory. A migration will abort if progress is stalled for 240 seconds. Concurrent outgoing migrations are limited to one per CPU core per host, or 2, whichever is smaller. See https://access.redhat.com/solutions/744423 for more details about tuning migration settings.

Commands:
4.355. xorg-x11-drv-nouveau 4.355.1. RHBA-2011:1600 - xorg-x11-drv-nouveau bug fix and enhancement update Updated xorg-x11-drv-nouveau packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-nouveau utility provides the Xorg X11 Nouveau video driver for NVIDIA graphics chipsets. Bug Fix BZ# 708500 Prior to this update, one process was used to scan for all defects. As a result, xorg-x11-drv-nouveau packages did not build without patches against its supporting components. This update scans defects in downstream patches separately. Now, the packages build as expected when not all downstream patches are present. Enhancement BZ# 713768 This update adds the updated Xorg Nouveau driver for NVIDIA GeForce/Quadro hardware to the xorg-x11-drv-nouveau package. All users of the Xorg x11 Nouveau driver, are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Chapter 80. token This chapter describes the commands under the token command. 80.1. token issue Issue new token Usage: Table 80.1. Optional Arguments Value Summary -h, --help Show this help message and exit Table 80.2. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 80.3. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 80.4. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 80.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 80.2. token revoke Revoke existing token Usage: Table 80.6. Positional Arguments Value Summary <token> Token to be deleted Table 80.7. Optional Arguments Value Summary -h, --help Show this help message and exit

Commands:
openstack token issue [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty]
openstack token revoke [-h] <token>
Assessing and Monitoring Security Vulnerabilities on RHEL Systems Red Hat Insights 1-latest Understanding your Environmental Exposure to Potential Security Threats Red Hat Customer Content Services

Commands:
USE [master] GO CREATE LOGIN [assessmentLogin] with PASSWORD= N'<*PASSWORD*>' ALTER SERVER ROLE [sysadmin] ADD MEMBER [assessmentLogin] GO
echo "assessmentLogin" > /var/opt/mssql/secrets/assessment echo "<*PASSWORD*>" >> /var/opt/mssql/secrets/assessment
chmod 0600 /var/opt/mssql/secrets/assessment chown mssql:mssql /var/opt/mssql/secrets/assessment
yum -y install powershell
su mssql -c "/usr/bin/pwsh -Command Install-Module SqlServer"
/bin/curl -LJ0 -o /opt/mssql/bin/runassessment.ps1 https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/sql-assessment-api/RHEL/runassessment.ps1 chown mssql:mssql /opt/mssql/bin/runassessment.ps1 chmod 0700 /opt/mssql/bin/runassessment.ps1
mkdir /var/opt/mssql/log/assessments/ chown mssql:mssql /var/opt/mssql/log/assessments/ chmod 0700 /var/opt/mssql/log/assessments/
su mssql -c "pwsh -File /opt/mssql/bin/runassessment.ps1"
insights-client
cp mssql-runassessment.service /etc/systemd/system/ cp mssql-runassessment.timer /etc/systemd/system/ chmod 644 /etc/systemd/system/
systemctl enable --now mssql-runassessment.timer
insights-client --group=<name-you-choose>
tags --- group: eastern-sap name: Jane Example contact: jexample@corporate.com Zone: eastern time zone Location: - gray_rack - basement Application: SAP
tags --- group: eastern-sap location: Boston description: - RHEL8 - SAP key 4: value
insights-client
vi /etc/insights-client/tags.yaml
cat /etc/insights-client/tags.yaml group: redhat location: Brisbane/Australia description: - RHEL8 - SAP security: strict network_performance: latency
insights-client
14.4. User-Defined Functions Support In Teiid Designer you can create, manage and use User-Defined Functions (UDFs). These functions allow you to perform simple or complex Java operations on your data during runtime. This is accomplished by deploying your custom UDF jars on your server and creating a scalar function representation of your function method to use in your view transformation. In the VDB Editor, you have the option of including your UDF jars as part of the VDB artifact. If included in the VDB, the jars will automatically be deployed to the server for you when the VDB is deployed. When a UDF model is added to a VDB, each scalar function is interrogated and its referenced UDF jar (if available) is added to the VDB as well as shown in the UDF Jars tab in the editor

Commands:
Chapter 3. Red Hat build of OpenJDK 11.0.16.1 release notes Review the following release notes for an overview of the changes from the Red Hat build of OpenJDK 11.0.16.1 patch release: Fixed issue with the C2 JIT compiler The Red Hat build of OpenJDK 11.0.16.1 release fixes a regression issue with the C2 Just-In-Time (JIT) compiler, which caused the HotSpot JVM to unexpectedly crash. See, JDK-8292396 (JDK Bug System) Advisories related to the Red Hat build of OpenJDK 11.0.16.1 release The following advisories have been issued about bug fixes and CVE fixes included in this release: RHBA-2022:6294-01 RHBA-2022:6349-01

Commands:
3.3.6. Converting a virtual machine running Windows This example demonstrates converting a local (libvirt-managed) Xen virtual machine running Windows for output to Red Hat Enterprise Virtualization. Ensure that the virtual machine's XML is available locally, and that the storage referred to in the XML is available locally at the same paths. To convert the guest virtual machine from an XML file, run: Where guest_name.xml is the path to the virtual machine's exported XML, and storage.example.com:/exportdomain is the export storage domain. You may also use the --network parameter to connect to a locally managed network if your virtual machine only has a single network interface. If your virtual machine has multiple network interfaces, edit /etc/virt-v2v.conf to specify the network mapping for all interfaces. If your virtual machine uses a Xen paravirtualized kernel (it would be called something like kernel-xen or kernel-xenU ), virt-v2v will attempt to install a new kernel during the conversion process. You can avoid this requirement by installing a regular kernel, which will not reference a hypervisor in its name, alongside the Xen kernel prior to conversion. You should not make this newly installed kernel your default kernel, because Xen will not boot it. virt-v2v will make it the default during conversion.

Commands:
virt-v2v -i libvirtxml -o rhev -osd storage.example.com:/exportdomain --network rhevm guest_name.xml
12.3. Translator Properties Translators can have a number of configurable properties. These are divided among the following categories: Execution Properties - these properties determine aspects of how data is retrieved. A list of properties common to all translators are provided in Section 12.5, "Base Execution Properties" . Note The execution properties for a translator typically have reasonable defaults. For specific translator types, base execution properties are already tuned to match the source. In most cases the user will not need to adjust their values. Importer Properties - these properties determine what metadata is read for import. There are no common importer properties. Note The import capabilities of translators is currently only used by dynamic VDBs and not by Teiid Designer. See Section 6.6, "Dynamic VDBs" .

Commands:
Chapter 7. Connecting to external services You can connect a router to an external service such as a message broker. The services may be running in the same OpenShift cluster as the router network, or running outside of OpenShift. Prerequisites You must have access to a message broker. Procedure This procedure describes how to connect a router to a broker and configure a link route to connect messaging clients to it. Start editing the Interconnect Custom Resource YAML file that describes the router deployment that you want to connect to a broker. In the spec section, configure the connection and link route. Sample router-mesh.yaml file apiVersion: interconnectedcloud.github.io/v1alpha1 kind: Interconnect metadata: name: router-mesh spec: ... connectors: 1 - name: my-broker host: broker port: 5672 routeContainer: true linkRoutes: 2 - prefix: q1 direction: in connection: my-broker - prefix: q1 direction: out connection: my-broker 1 The connection to be used to connect this router to the message broker. The Operator will configure this connection from every router defined in this router deployment to the broker. If you only want a single connection between the router network and the broker, then configure a listener instead of a connector and have the broker establish the connection. 2 The link route configuration. It defines the incoming and outgoing links and connection to be used to connect messaging applications to the message broker. Verify that the router has established the link route to the message broker. Additional resources For more information about link routes, see Creating link routes .

Commands:
oc edit -f router-mesh.yaml
apiVersion: interconnectedcloud.github.io/v1alpha1 kind: Interconnect metadata: name: router-mesh spec: connectors: 1 - name: my-broker host: broker port: 5672 routeContainer: true linkRoutes: 2 - prefix: q1 direction: in connection: my-broker - prefix: q1 direction: out connection: my-broker
oc exec router-mesh-fb6bc5797-crvb6 -it -- qdstat --linkroutes Link Routes address dir distrib status ==================================== q1 in linkBalanced active q1 out linkBalanced active
Chapter 5. Example Script

Commands:
#!/usr/bin/env python import sys import requests from datetime import datetime, timedelta API_HOST = 'https://access.redhat.com/hydra/rest/securitydata' PROXIES = {} uncomment lines below to specify proxy server HTTPS_PROXY = "http://yourproxy.example.com:8000" PROXIES = { "https" : HTTPS_PROXY } def get_data(query): full_query = API_HOST + query r = requests.get(full_query, proxies=PROXIES) if r.status_code != 200: print('ERROR: Invalid request; returned {} for the following ' 'query:\n{}'.format(r.status_code, full_query)) sys.exit(1) if not r.json(): print('No data returned with the following query:') print(full_query) sys.exit(0) return r.json() Get a list of issues and their impacts for RHSA-2022:1988 endpoint = '/cve.json' params = 'advisory=RHSA-2022:1988' data = get_data(endpoint + '?' + params) for cve in data: print(cve['CVE'], cve['severity']) print('-----') Get a list of kernel advisories for the last 30 days and display the packages that they provided. endpoint = '/csaf.json' date = datetime.now() - timedelta(days=30) params = 'package=kernel&after=' + str(date.date()) data = get_data(endpoint + '?' + params) kernel_advisories = [] for advisory in data: print(advisory['RHSA'], advisory['severity'], advisory['released_on']) print('-', '\n- '.join(advisory['released_packages'])) kernel_advisories.append(advisory['RHSA']) print('-----') From the list of advisories saved in the previous example (as `kernel_advisories`), get a list of affected products for each advisory. endpoint = '/csaf/' for advisory in kernel_advisories: data = get_data(endpoint + advisory + '.json') print(advisory) for product_branch in data['product_tree']['branches']: for inner_branch in product_branch['branches'][0]['branches']: print('-', inner_branch['name'])
Workloads APIs OpenShift Container Platform 4.17 Reference guide for workloads APIs Red Hat OpenShift Documentation Team

Commands:
"postCommit": { "script": "rake test --verbose", }
The above is a convenient form which is equivalent to:
"postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] }
"postCommit": { "commit": ["rake", "test", "--verbose"] }
Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint.
"postCommit": { "args": ["rake", "test", "--verbose"] }
This form is only useful if the image entrypoint can handle arguments.
"postCommit": { "script": "rake test USD1", "args": ["--verbose"] }
This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, USD0 will be "/bin/sh" and USD1, USD2, etc, are the positional arguments from Args.
"postCommit": { "command": ["rake", "test"], "args": ["--verbose"] }
This form is equivalent to appending the arguments to the Command slice.
"postCommit": { "script": "rake test --verbose", }
The above is a convenient form which is equivalent to:
"postCommit": { "command": ["/bin/sh", "-ic"], "args": ["rake test --verbose"] }
"postCommit": { "commit": ["rake", "test", "--verbose"] }
Command overrides the image entrypoint in the exec form, as documented in Docker: https://docs.docker.com/engine/reference/builder/#entrypoint.
"postCommit": { "args": ["rake", "test", "--verbose"] }
This form is only useful if the image entrypoint can handle arguments.
"postCommit": { "script": "rake test USD1", "args": ["--verbose"] }
This form is useful if you need to pass arguments that would otherwise be hard to quote properly in the shell script. In the script, USD0 will be "/bin/sh" and USD1, USD2, etc, are the positional arguments from Args.
"postCommit": { "command": ["rake", "test"], "args": ["--verbose"] }
This form is equivalent to appending the arguments to the Command slice.
Appendix B. Accessing Red Hat Documentation B.1. Product Documentation Red Hat Product Documentation located at https://access.redhat.com/site/documentation/ serves as a central source of information. It is currently translated in 22 languages and for each product, it provides different kinds of books from release and technical notes to installation, user, and reference guides in HTML, PDF, and EPUB formats. The following is a brief list of documents that are directly or indirectly relevant to this book: The Red Hat Enterprise Linux 7 System Administrator's Guide , available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/System_Administrators_Guide/index.html , contains detailed information about various system components, for instance the GRUB 2 boot loader, package management, systemd , or printer configuration. The Red Hat Enterprise Linux 7 Installation Guide , available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/index.html , contains detailed information about installing Red Hat Enterprise Linux 7 and using the Anaconda installer. The Red Hat Enterprise Linux 7 Migration Planning Guide , available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Migration_Planning_Guide/index.html , contains an overview of major changes in behavior and compatibility between Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7. The Migration Planning Guide also introduces the tools provided by Red Hat to assist with upgrades to Red Hat Enterprise Linux 7. The Red Hat Enterprise Linux 7 Networking Guide , available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Networking_Guide/index.html , contains information about configuration and administration of networking for Red Hat Enterprise Linux 7. The Red Hat Enterprise Linux 7 Virtualization Deployment and Administration Guide , available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/ , contains information about installing, configuring, and managing Red Hat Enterprise Linux virtualization.

Commands:
8.207. spice-xpi 8.207.1. RHEA-2013:1667 - spice-xpi bug fix and enhancement update Updated spice-xpi packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The spice-xpi packages provide the Simple Protocol for Independent Computing Environments (SPICE) extension for Mozilla that allows the SPICE client to be used from a web browser. Bug Fix BZ# 882339 Prior to this update, the spice-xpi browser plug-in did not remove the /tmp/spicec-XXXXXX/spice-foreign socket and the /tmp/spicec-XXXXXX/ directory, so they were still present after client had exited. This bug has been fixed, and the browser plug-in now removes the above mentioned file and directory after client exits. Enhancement BZ# 994613 Proxy support for SPICE connection has been added to the spice-xpi browser plug-in. With this update, spice-xpi is now able to pass the proxy setting to the SPICE client it spawns, for example, when opening a console from the Red Hat Enterprise Virtualization Manager portal. Users of spice-xpi are advised to upgrade to these updated packages, which fix this bug and add this enhancement. After installing the update, Firefox must be restarted for the changes to take effect.

Commands:
5.3. Deployment 389-ds-base component, BZ# 878111 The ns-slapd utility terminates unexpectedly if it cannot rename the dirsrv- <instance> log files in the /var/log/ directory due to incorrect permissions on the directory. cpuspeed component, BZ# 626893 Some HP Proliant servers may report incorrect CPU frequency values in /proc/cpuinfo or /sys/device/system/cpu/*/cpufreq . This is due to the firmware manipulating the CPU frequency without providing any notification to the operating system. To avoid this ensure that the HP Power Regulator option in the BIOS is set to OS Control . An alternative available on more recent systems is to set Collaborative Power Control to Enabled . releng component, BZ# 644778 Some packages in the Optional repositories on RHN have multilib file conflicts. Consequently, these packages cannot have both the primary architecture (for example, x86_64) and secondary architecture (for example, i686) copies of the package installed on the same machine simultaneously. To work around this issue, install only one copy of the conflicting package. grub component, BZ# 695951 On certain UEFI-based systems, you may need to type BOOTX64 rather than bootx64 to boot the installer due to case sensitivity issues. grub component, BZ# 698708 When rebuilding the grub package on the x86_64 architecture, the glibc-static.i686 package must be used. Using the glibc-static.x86_64 package will not meet the build requirements.

Commands: