mtpti5iD/redhat-docs_dataset huggingface dataset:
4.49. dosfstools 4.49.1. RHBA-2011:1552 - dosfstools bug fix update An updated dosfstools package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The dosfstools package contains a set of tools for creating and maintaining FAT-type file systems. It includes the mkdosfs and dosfsck utilities, which make and check MS-DOS FAT file systems on hard drives and floppy disks. Bug Fixes BZ# 624596 Previously, when the dosfsck and the dosfslabel utilities were executed on the IBM System z architecture using a FAT32 file system, they terminated with this error message: "Logical sector size is zero". This was caused by unaligned fields which were first byte-wise copied. With this fix, the fields are not pre-copied any more, but are accessed the same way as on the i686 architecture. BZ# 677789 The fsck.vfat utility terminated due to buffer overflow. This occurred when checking a device with the corrupted VFAT file system if there were any chains of orphaned clusters. The name of the newly created file that contained these clusters was printed directly into the name field, which led to an out of boundary write. The name is now printed into the buffer and individual parts are then correctly copied into the appropriate field. BZ# 688128 The dosfslabel utility displayed an error message when labeling the FAT32 file system due to some of its internal structures being initialized incorrectly. The dosfslabel utility now reads the FAT file system first, which fixes the problem. BZ# 709266 The mkfs.vfat utility did not correctly detect device partitions on RAID devices. As a consequence, formatting failed with an error message. This was caused by an invalid mask for the statbuf.st_rdev variable. The mask has been fixed to be at least four bytes long and the problem no longer occurs. All users of dosfstools are advised to upgrade to this updated package, which resolves these bugs.

Commands:
B.15.5. RHBA-2011:0173 - device-mapper-multipath bug fix update Updated device-mapper-multipath packages that resolve an issue are now available for Red Hat Enterprise Linux 6. The device-mapper-multipath packages provide tools to manage multipath devices by giving the "dm-multipath" kernel module instructions on what to do, as well as by managing the creation and removal of partitions for Device-Mapper devices. Bug Fix BZ# 658937 When all paths of a pathgroup with set group_by_prio were restored after a failure, multipathd could place some paths into a wrong pathgroup. This issue occurred, because the daemon checked if pathgroups needed reconfiguration only if a path priority changed. When the original paths were restored, they could have been assigned the same priority as before the failure. In such case the paths were incorrectly left in a wrong pathgroup. With this update, when checking if it needs to recalculate the pathgroups, the multipathd daemon refreshes and checks all priorities once a new path becomes available and places recovered paths into the correct pathgroup. All users of device-mapper-multipath are advised to upgrade to these updated packages, which resolve this issue.

Commands:
5.5.3. The UserDir Directive The UserDir directive is disabled by default because it can confirm the presence of a user account on the system. To enable user directory browsing on the server, use the following directives: These directives activate user directory browsing for all user directories other than /root/ . To add users to the list of disabled accounts, add a space delimited list of users on the UserDir disabled line.

Commands:
UserDir enabled UserDir disabled root
4.17. bfa-firmware 4.17.1. RHBA-2011:1759 - bfa-firmware bug fix and enhancement update An updated bfa-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The bfa-firmware package contains the Brocade Fibre Channel Host Bus Adapter (HBA) Firmware to run Brocade Fibre Channel and CNA adapters. This package also supports the Brocade BNA network adapter. The bfa-firmware package has been upgraded to upstream version 3.0.0.0, which provides a number of bug fixes and enhancements over the version. (BZ# 735142 ) All users of Brocade Fibre Channel and CNA adapters are advised to upgrade to this updated package, which fixes several bugs and adds various enhancements.

Commands:
11.9. Configuring netconsole The netconsole kernel module enables logging of kernel messages over the network to another computer. It allows kernel debugging when disk logging fails or when using the serial console is not possible. Configuring a Listening Machine To enable receiving netconsole logging messages, install the rsyslog package: To configure rsyslogd to listen on the 514/UDP port and receive messages from the network, uncomment the following lines in the MODULES section of /etc/rsyslog.conf : Restart the rsyslogd service for the changes to take effect: To verify that rsyslogd is listening on the 514/udp port, use the following command: The 0 *:syslog value in the netstat -l output mean that rsyslogd is listening on default netconsole port, which is defined in the /etc/services file: Configuring a Sending Machine In Red Hat Enterprise Linux 6, netconsole is configured using the file /etc/sysconfig/netconsole , which is part of the initscripts package. This package is installed by default and it also provides the netconsole service. To configure a sending machine, set the value of the SYSLOGADDR variable in the /etc/sysconfig/netconsole file to match the IP address of the syslogd server, for example: Restart the netconsole service so the changes take effect. Then, use the chkconfig command to ensure netconsole service starts automatically after reboot: By default, the rsyslogd server writes the netconsole messages from the client in /var/log/messages or in the file specified in rsyslog.conf . Note To set rsyslogd and netconsole to use a different port, change the following line in /etc/rsyslog.conf to the desired port number: On the sending machine, uncomment and edit the following line in the /etc/sysconfig/netconsole file: For more information about netconsole configuration and troubleshooting tips, see Netconsole Kernel Documentation .

Commands:
]# yum install rsyslog
USDModLoad imudp USDUDPServerRun 514
]# service rsyslog restart
]# netstat -l | grep syslog udp 0 0 *:syslog *:* udp 0 0 *:syslog *:*
]USD cat /etc/services | grep syslog syslog 514/udp syslog-conn 601/tcp # Reliable Syslog Service syslog-conn 601/udp # Reliable Syslog Service syslog-tls 6514/tcp # Syslog over TLS
SYSLOGADDR= 192.168.0.1
]# service netconsole restart Initializing netconsole [ OK ] ]# chkconfig netconsole on
USDUDPServerRun <PORT>
SYSLOGPORT=514
Workloads APIs OpenShift Container Platform 4.14 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.
IP: An IP address allocated to the pod. Routable at least within the cluster.
Chapter 3. Known issues The dnf command is not available. To reduce image size, .NET 9.0 container images use the ubi-minimal base image instead of the ubi base image. The ubi-minimal image uses the microdnf command as its package manager instead of the dnf command. If your Dockerfiles/Containerfiles use the dnf command, you must change them to use the microdnf command instead. For more information about the microdnf command, please see the microdnf man page on your system. Support for the DOTNET_SSL_DIRS environment variable used to load certificates from additional directories has been removed in favor of using the SSL_CERT_DIR environment variable that is supported since .NET 8.0. The runtime image no longer supports source-to-image (S2I) building an application image from pre-built .NET artifacts. Users are encouraged to use the .NET SDK directly to build application images layered on a runtime image. The SDK image may be used as a workaround because it also supports building from pre-built .NET artifacts. The resulting application image will then be based on the SDK image rather than the runtime image. See Known Issues in the .NET 9.0 Release Notes for .NET 9.0 RPM packages for a list of known issues and workarounds for RPMs.

Commands:
7.143. openjpeg 7.143.1. RHBA-2014:2001 - openjpeg bug fix update Updated openjpeg packages that fix one bug are now available for Red Hat Enterprise Linux 6. OpenJPEG is an open source library for reading and writing image files in JPEG 2000 format. Bug Fix BZ# 1047494 Due to a regression introduced in the version of the openjpeg packages, chroma-subsampled images became corrupted during decoding. An upstream patch has been applied to fix this bug, and the images are now decoded correctly. Users of openjpeg are advised to upgrade to these updated packages, which fix this bug. All running applications using OpenJPEG must be restarted for the update to take effect.

Commands:
Common object reference OpenShift Container Platform 4.18 Reference guide common API objects Red Hat OpenShift Documentation Team

Commands:
<quantity> ::= <signedNumber><suffix>
(Note that <suffix> may be empty, from the "" case in <decimalSI>.)
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.Object `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.RawExtension `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
{ "kind":"MyAPIObject", "apiVersion":"v1", "myPlugin": { "kind":"PluginA", "aOption":"foo", }, }
14.3. Enabling Spring Cache Support (Remote Client-Server Mode) Spring's cache support can be enabled, for both Spring3 and Spring4, either through the xml file or programmatically in the application. Declarative Configuration To enable Spring support declaratively perform the following steps: Add <cache:annotation-driven/> to the xml file. This line enables the standard spring annotations to be used by the application. Define the HotRod client properties using the <infinispan:remote-cache-manager ... /> . The following example demonstrates these changes: Example 14.6. Sample Declarative Configuration Programmatic Configuration To enable Spring support programmatically perform the following steps: Add the @EnableCaching annotation to the Spring configuration class in use. Define a method returning a SpringRemoteCacheManager annotated with @Bean . The following code snippet highlights these changes: Example 14.7. Sample Programmatic Configuration Report a bug

Commands:
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:infinispan="http://www.infinispan.org/schemas/spring" xmlns:cache="http://www.springframework.org/schema/cache" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/cache http://www.springframework.org/schema/cache/spring-cache.xsd http://www.infinispan.org/schemas/spring http://www.infinispan.org/schemas/infinispan-spring.xsd"> [...] <cache:annotation-driven/> <infinispan:remote-cache-manager configuration="classpath:/path/to/hotrod-client.properties"/> [...]
import org.infinispan.client.hotrod.RemoteCacheManager; import org.infinispan.client.hotrod.configuration.Configuration; import org.infinispan.client.hotrod.configuration.ConfigurationBuilder; import org.infinispan.spring.provider.SpringRemoteCacheManager; import org.springframework.cache.annotation.EnableCaching; import org.springframework.context.annotation.Bean; [...] @org.springframework.context.annotation.Configuration @EnableCaching public class Config { [...] @Bean public SpringRemoteCacheManager cacheManager() throws Exception { Configuration config = new ConfigurationBuilder() .addServer() .host(ADDRESS) .port(PORT) .build(); return SpringRemoteCacheManager(new RemoteCacheManager(config)); } [...]
7.184. pki-core 7.184.1. RHSA-2013:0511 - Moderate: pki-core security, bug fix and enhancement update Updated pki-core packages that fix multiple security issues, two bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Red Hat Certificate System is an enterprise software system designed to manage enterprise public key infrastructure (PKI) deployments. PKI Core contains fundamental packages required by Red Hat Certificate System, which comprise the Certificate Authority (CA) subsystem. Security Fix CVE-2012-4543 Note: The Certificate Authority component provided by this advisory cannot be used as a standalone server. It is installed and operates as a part of Identity Management (the IPA component) in Red Hat Enterprise Linux. Multiple cross-site scripting flaws were discovered in Certificate System. An attacker could use these flaws to perform a cross-site scripting (XSS) attack against victims using Certificate System's web interface. Bug Fixes BZ#841663 Previously, due to incorrect conversion of large integers while generating a new serial number, some of the most significant bits in the serial number were truncated. Consequently, the serial number generated for certificates was sometimes smaller than expected and this incorrect conversion in turn led to a collision if a certificate with the smaller number already existed in the database. This update removes the incorrect integer conversion so that no serial numbers are truncated. As a result, the installation wizard proceeds as expected. BZ#844459 The certificate authority used a different profile for issuing the audit certificate than it used for renewing it. The issuing profile was for two years, and the renewal was for six months. They should both be for two years. This update sets the default and constraint parameters in the caSignedLogCert.cfg audit certificate renewal profile to two years. Enhancements BZ# 858864 IPA (Identity, Policy and Audit) now provides an improved way to determine that PKI is up and ready to service requests. Checking the service status was not sufficient. This update creates a mechanism for clients to determine that the PKI subsystem is up using the getStatus() function to query the cs.startup_state in CS.cfg. BZ# 891985 This update increases the default root CA validity period from eight years to twenty years. All users of pki-core are advised to upgrade to these updated packages, which fix these issues and add these enhancements.

Commands:
5.9.9.2. Rebuilding a RAID array Should /proc/mdstat show that a problem exists with one of the RAID arrays, you can rebuild it by performing the following steps: Remove the disk from the raid array. mdadm --manage /dev/md0 -r /dev/sdc3 Remove the disk from the system. Using fdisk , replace the removed disk and re-format the replacement disk. Add the new disk back to the RAID array. mdadm --manage /dev/md0 -a /dev/sdc3 To restore the disk, perform a "software fail" the spare slice: mdadm --manage --set-faulty /dev/md0 /dev/sdc3 The system will now attempt to rebuild the array on the replaced disk. Use the following command to monitor status: watch -n 1 cat /proc/mdstat When the array is finished rebuilding, remove and then re-add the software-failed disk back to the array. mdadm --manage /dev/md0 -r /dev/sdc3 mdadm --manage /dev/md0 -a /dev/sdc3 Check the array. mdadm --detail /dev/md0

Commands:
Chapter 1. Introduction to Red Hat OpenStack bare-metal hardware certification policies The Red Hat OpenStack Platform (RHOSP) bare-metal hardware certification policy guide is intended for hardware vendors who want to certify their bare-metal servers with Red Hat. The RHOSP bare-metal certification tests ensures that you can orchestrate your servers automatically without manual intervention. Through this program, if the servers meet the requirements you can certify your servers for the IPI component by deploying it on the Red Hat OpenStack Platform. 1.1. Audience This guide is intended for Partners who offer their own infrastructure hardware like system servers, or management controllers for use with Red Hat OpenStack Platform in a supported customer environment. 1.2. Overview of the program The Red Hat OpenStack Platform (RHOSP) bare-metal hardware certification creates value for customers, because the systems can be managed and automatically deployed and redeployed with Red Hat OpenStack bare-metal hardware without manual intervention. The certification process, through a series of tests, validates that a certified solution meets the requirements of an enterprise cloud, and is jointly supported by Red Hat and your organization. The RHOSP bare-metal hardware certification program policies include multiple tests each with a series of subtests and checks, which are explained in the document.

Commands:
7.30. cpupowerutils 7.30.1. RHEA-2015:1437 - cpupowerutils enhancement update Updated cpupowerutils packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The cpupowerutils packages provide a suite of tools to manage power states on appropriately enabled central processing units (CPU). Enhancement BZ# 1187332 The turbostat utility now supports the 6th Generation Intel Core Processors - for mobile and desktop. Users of cpupowerutils are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 5. Validating your OpenStack cloud with the Integration Test Suite (tempest) You can run Integration Test Suite validations in many ways with the tempest run command. You can also combine multiple options in a single tempest run command. 5.1. Prerequisites An OpenStack environment that contains the Integration Test Suite packages. For more information, see Installing the Integration Test Suite with director . An Integration Test Suite configuration that corresponds to your OpenStack environment. For more information, see Creating a workspace . 5.2. Listing available tests Use the --list-tests option to list all available tests. Procedure Enter the tempest run command with either the --list-tests or -l options to get a list of available tempest tests: 5.3. Running smoke tests Smoke testing is a type of preliminary testing which covers only the most important functionality. Although these tests are not comprehensive, running smoke tests can save time if they do identify a problem. Procedure Enter the tempest run command with the --smoke option: 5.4. Passing tests by using allowlist files An allowlist file is a file that contains regular expressions to select tests that you want to include. If you use one or more regular expressions, specify each expression on a separate line. Procedure Enter the tempest run command with either the --whitelist-file or -w options to use an allowlist file: 5.5. Skipping tests by using blocklist files A blocklist file is a file that contains regular expressions to select tests that you want to exclude. If you use one or more regular expressions, specify each expression on a separate line. Procedure Enter the tempest run command with either the --blacklist-file or -b options to use a blocklist file: 5.6. Running tests in parallel or in series You can run tests in parallel, or in series. You can also define the number of workers that you want to use when you run parallel tests. By default, the Integration Test Suite uses one worker for each CPU available. Choose to run the tests serially or in parallel: Run the tests serially: Run the tests in parallel (default): Use the --concurrency or -c option to specify the number of workers to use when you run tests in parallel: 5.7. Running specific tests Run specific tests with the --regex option. The regular expression must be Python regular expression: Procedure Enter the following command: For example, use the following example command to run all tests that have names that begin with tempest.scenario : 5.8. Deleting Integration Test Suite objects Enter the tempest cleanup command to delete all Integration Test Suite (tempest) resources. This command also deletes projects, but the command does not delete the administrator account: Procedure Delete the tempest resources:

Commands:
tempest run -l
tempest run --smoke
tempest run -w <whitelist_file>
tempest run -b <blacklist_file>
tempest run --serial
tempest run --parallel
tempest run --concurrency <workers>
tempest run --regex <regex>
tempest run --regex ^tempest.scenario
tempest cleanup --delete-tempest-conf-objects
Chapter 3. Red Hat JBoss Web Server metering labels for Red Hat OpenShift You can add metering labels to your Red Hat JBoss Web Server pods and check Red Hat subscription details with the OpenShift Metering Operator. Note Do not add metering labels to any pods that an operator or a template deploys and manages. You can apply labels to pods using the Metering Operator on OpenShift Container Platform version 4.8 and earlier. From version 4.9 onward, the Metering Operator is no longer available without a direct replacement. Red Hat JBoss Web Server can use the following metering labels: com.company: Red_Hat rht.prod_name: Red_Hat_Runtimes rht.prod_ver: 2023-Q4 rht.comp: JBoss_Web_Server rht.comp_ver: 6.0.0 rht.subcomp: Tomcat 10 rht.subcomp_t: application Additional resources Configuring and using Metering in OpenShift Container Platform

Commands:
Chapter 2. About Eclipse Vert.x Eclipse Vert.x is a toolkit used for creating reactive, non-blocking, and asynchronous applications that run on Java Virtual Machine. (JVM). It contains several components that help you create reactive applications. It is designed to be cloud-native. Since Eclipse Vert.x supports asynchronous applications it can be used to create applications with high volume of messages, large event processing, HTTP interactions, and so on.

Commands: