mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Red Hat Insights policies service overview Policies evaluate system configurations in your environment, and can send notifications when changes occur. Policies you create are applicable to all systems in your Insights inventory. You can create and manage policies using the Red Hat Insights for Red Hat Enterprise Linux user interface in the Red Hat Hybrid Cloud Console, or using the Insights API. Policies can assist you by managing tasks such as: Raising an alert when particular conditions occur in your system configuration. Emailing a team when security packages are out of date on a system. Using policies to monitor configuration changes in your inventory and notifying by email requires: Setting user email preferences (if not already set). Creating a policy to detect configuration changes as a trigger and selecting email as the trigger action. Note Configure User Access in Red Hat Hybrid Cloud Console > the Settings icon (⚙) > Identity & Access Management > User Access > Users . See User Access Configuration Guide for Role-based Access Control (RBAC) with FedRAMP for more information about this feature and example use cases. 1.1. User Access settings in the Red Hat Hybrid Cloud Console All users on your account have access to most of the data in Insights for Red Hat Enterprise Linux. 1.1.1. Predefined User Access groups and roles To make groups and roles easier to manage, Red Hat provides two predefined groups and a set of predefined roles. 1.1.1.1. Predefined groups The Default access group contains all users in your organization. Many predefined roles are assigned to this group. It is automatically updated by Red Hat. Note If the Organization Administrator makes changes to the Default access group its name changes to Custom default access group and it is no longer updated by Red Hat. The Default admin access group contains only users who have Organization Administrator permissions. This group is automatically maintained and users and roles in this group cannot be changed. 1.1.2. User Access roles for the Policies service The following predefined roles on the Red Hat Hybrid Cloud Console enable access to policies features in Insights for Red Hat Enterprise Linux: Policies administrator role. The Policies administrator role provides read and write access allowing these users to perform any available operation on policies resources. This predefined role is in the Default admin access group . Policies viewer role. The Policies viewer role provides read-only access. (If your organization determines that the default configuration of the Policies viewer role is inadequate, a User Access administrator can create a custom role with the specific permissions that you need.) This predefined role is in the Default access group . Note If you configured groups before April 2023, any user who was not an Organization Administrator will have the Policies administrator role replaced with the Policies viewer role. Modifications made to the Default access group before April are not changed. Additional Resources How to use User Access in the User Access Configuration Guide for Role-based Access Control (RBAC). Predefined User Access roles

Commands:
26.8. Installing a CA Into an Existing IdM Domain If an IdM domain was installed without a Certificate Authority (CA), you can install the CA services subsequently. Depending on your environment, you can install the IdM Certificate Server CA or use an external CA. Note For details on the supported CA configurations, see Section 2.3.2, "Determining What CA Configuration to Use" . Installing an IdM Certificate Server Use the following command to install the IdM Certificate Server CA: Run the ipa-certupdate utility on all servers and clients to update them with the information about the new certificate from LDAP. You must run ipa-certupdate on every server and client separately. Important Always run ipa-certupdate after manually installing a certificate. If you do not, the certificate will not be distributed to the other machines. Installing External CA The subsequent installation of an external CA consists of multiple steps: Start the installation: After this step an information is shown that a certificate signing request (CSR) was saved. Submit the CSR to the external CA and copy the issued certificate to the IdM server. Continue the installation with passing the certificates and full path to the external CA files to ipa-ca-install : Run the ipa-certupdate utility on all servers and clients to update them with the information about the new certificate from LDAP. You must run ipa-certupdate on every server and client separately. Important Always run ipa-certupdate after manually installing a certificate. If you do not, the certificate will not be distributed to the other machines. The CA installation does not replace the existing service certificates for the LDAP and web server with ones issued by the new installed CA. For details how to replace the certificates, see Section 26.9, "Replacing the Web Server's and LDAP Server's Certificate" .

Commands:
[root@ipa-server ~] ipa-ca-install
[root@ipa-server ~] ipa-ca-install --external-ca
ipa-ca-install --external-cert-file=/root/ master .crt --external-cert-file=/root/ca.crt
11.2. Disabling vhost-net The vhost-net module is a kernel-level back end for virtio networking that reduces virtualization overhead by moving virtio packet processing tasks out of user space (the qemu process) and into the kernel (the vhost-net driver). vhost-net is only available for virtio network interfaces. If the vhost-net kernel module is loaded, it is enabled by default for all virtio interfaces, but can be disabled in the interface configuration in the case that a particular workload experiences a degradation in performance when vhost-net is in use. Specifically, when UDP traffic is sent from a host machine to a guest virtual machine on that host, performance degradation can occur if the guest virtual machine processes incoming data at a rate slower than the host machine sends it. In this situation, enabling vhost-net causes the UDP socket's receive buffer to overflow more quickly, which results in greater packet loss. It is therefore better to disable vhost-net in this situation to slow the traffic, and improve overall performance. To disable vhost-net , edit the <interface> sub-element in the guest virtual machine's XML configuration file and define the network as follows: Setting the driver name to qemu forces packet processing into qemu user space, effectively disabling vhost-net for that interface.

Commands:
<interface type="network"> <model type="virtio"/> <driver name="qemu"/> </interface>
4.190. net-tools 4.190.1. RHBA-2011:1596 - net-tools bug fix update An updated net-tools package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The net-tools package contains basic networking tools, including ifconfig, netstat, route, and others. Bug Fixes BZ# 705110 Prior to this update, the "hostname -i" command failed to display related network addresses when the hostname was not included in the /etc/hosts file. The "hostname -f" command had the same issue with Fully Qualified Domain Names (FQDNs). To fix this issue, new "--all-fqdns" (or "-A") and "--all-ip-addresses" (or "-I") options have been implemented for the hostname command. These options are independent on the /etc/hosts content. The "hostname -I" command now displays all network addresses for all configured network interfaces, and the "hostname -A" command displays all FQDNs for all configured network interfaces of the host. BZ# 725348 The "netstat -p" command output incorrectly displayed a number in the PID/Program name column instead of the program name. The code has been modified to fix this issue, and netstat now shows the correct program name in this column. BZ# 732984 The netstat utility truncated IPv6 UDP sockets when the "--notrim" (or "-T") option was specified. This update fixes the issue, and whole IPv6 addresses are now displayed for UDP sockets when using netstat with this option. BZ# 680837 The route(8) manual page now includes an explicit description of the "mss M" option. BZ# 694766 The SYNOPSIS section of the plipconfig(8) manual page and the usage output of the plipconfig command have been modified to show correct plipconfig options. All users of net-tools are advised to upgrade to this updated package, which resolves these issues. 4.190.2. RHBA-2012:0555 - net-tools bug fix update Updated net-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The net-tools packages contain basic networking tools. including hostname, ifconfig, netstat, or route. Bug Fix BZ# 816375 Running the "hostname" command with the "-A, --all-fqdns" or "-I, --all-ip-addresses" option to display all Fully Qualified Domain Names (FQDNs) or network addresses of the host failed with the "Hostname lookup failure" error if the machine's host name was not resolved in DNS. With this update, these options are no longer dependent on name resolution; all FQDNs and network addresses of the host are now displayed as expected even if the host name cannot be resolved or is not included in the /etc/hosts file. All users of net-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
35.2. Finishing an Upgrade Important Once you have rebooted your system after performing an upgrade, you should also perform a manual system update. Consult Section 35.1, "Updating Your System" for more information. If you chose to upgrade your system from a release rather than perform a fresh installation, you may want to examine the differences in the package set. Section 9.12.2, " Upgrading Using the Installer " , Section 16.14.2, " Upgrading Using the Installer " , or Section 23.12.1, " Upgrading Using the Installer " (depending on your system architecture) advised you to create a package listing for your original system. You can now use that listing to determine how to bring your new system close to the original system state. Most software repository configurations are stored in packages that end with the term release . Check the old package list for the repositories that were installed: If necessary, retrieve and install these packages from their original sources on the Internet. Follow the instructions at the originating site to install the repository configuration packages for use by yum and other software management tools on your Red Hat Enterprise Linux system. Then run the following commands to make a list of other missing software packages: Now use the file /tmp/pkgs-to-install.txt with the yum command to restore most or all of your old software: Important Due to changes in package complements between Red Hat Enterprise Linux releases, it is possible this method may not restore all the software on your system. You can use the routines above to again compare the software on your system, and remedy any problems you find.

Commands:
awk '{print USD1}' ~/old-pkglist.txt | grep 'releaseUSD'
awk '{print USD1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt
su -c 'yum install `cat /tmp/pkgs-to-install.txt`'
Preface Red Hat OpenShift Data Foundation supports deployment on existing Red Hat OpenShift Container Platform (RHOCP) bare metal clusters in connected or disconnected environments along with out-of-the-box support for proxy environments. Both internal and external OpenShift Data Foundation clusters are supported on bare metal. See Planning your deployment and Preparing to deploy OpenShift Data Foundation for more information about deployment requirements. To deploy OpenShift Data Foundation, follow the appropriate deployment process based on your requirement: Internal mode Deploy using local storage devices Deploy standalone Multicloud Object Gateway component External mode

Commands:
1.2. Installing the Ruby Software Development Kit Enable the required repositories: Install the Ruby Software Development Kit: Alternatively, you can install with gem :

Commands:
subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms --enable=rhel-8-for-x86_64-appstream-rpms --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms
dnf install rubygem-ovirt-engine-sdk4
gem install ovirt-engine-sdk
24.2.4. Directories Use the Directories page in the Performance tab to configure options for specific directories. This corresponds to the <Directory> directive. Figure 24.6. Directories Click the Edit button in the top right-hand corner to configure the Default Directory Options for all directories that are not specified in the Directory list below it. The options that you choose are listed as the Options directive within the <Directory> directive. You can configure the following options: ExecCGI - Allow execution of CGI scripts. CGI scripts are not executed if this option is not chosen. FollowSymLinks - Allow symbolic links to be followed. Includes - Allow server-side includes. IncludesNOEXEC - Allow server-side includes, but disable the #exec and #include commands in CGI scripts. Indexes - Display a formatted list of the directory's contents, if no DirectoryIndex (such as index.html ) exists in the requested directory. Multiview - Support content-negotiated multiviews; this option is disabled by default. SymLinksIfOwnerMatch - Only follow symbolic links if the target file or directory has the same owner as the link. To specify options for specific directories, click the Add button beside the Directory list box. A window as shown in Figure 24.7, "Directory Settings" appears. Enter the directory to configure in the Directory text field at the bottom of the window. Select the options in the right-hand list and configure the Order directive with the left-hand side options. The Order directive controls the order in which allow and deny directives are evaluated. In the Allow hosts from and Deny hosts from text field, you can specify one of the following: Allow all hosts - Type all to allow access to all hosts. Partial domain name - Allow all hosts whose names match or end with the specified string. Full IP address - Allow access to a specific IP address. A subnet - Such as 192.168.1.0/255.255.255.0 A network CIDR specification - such as 10.3.0.0/16 Figure 24.7. Directory Settings If you check the Let .htaccess files override directory options , the configuration directives in the .htaccess file take precedence.

Commands:
3.2. Ignoring Local Disks when Generating Multipath Devices Some machines have local SCSI cards for their internal disks. DM-Multipath is not recommended for these devices. The following procedure shows how to modify the multipath configuration file to ignore the local disks when configuring multipath. Determine which disks are the internal disks and mark them as the ones to blacklist. In this example, /dev/sda is the internal disk. Note that as originally configured in the default multipath configuration file, executing the multipath -v2 shows the local disk, /dev/sda , in the multipath map. For further information on the multipath command output, see Section 5.1, "Multipath Command Output" . In order to prevent the device mapper from mapping /dev/sda in its multipath maps, edit the devnode_blacklist section of the /etc/multipath.conf file to include this device. Although you could blacklist the sda device using a devnode type, that would not be safe procedure since /dev/sda is not guaranteed to be the same on reboot. To blacklist individual devices, you can blacklist using the WWID of that device. Note that in the output to the multipath -vs command, the WWID of the /dev/sda device is SIBM-ESXSST336732LC____F3ET0EP0Q000072428BX1. To blacklist this device, include the following in the /etc/multipath.conf file. Run the following commands: The local disk or disks should no longer be listed in the new multipath maps, as shown in the following example.

Commands:
multipath -v2 create: SIBM-ESXSST336732LC____F3ET0EP0Q000072428BX1 [size=33 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 0:0:0:0 sda 8:0 [--------- device-mapper ioctl cmd 9 failed: Invalid argument device-mapper ioctl cmd 14 failed: No such device or address create: 3600a0b80001327d80000006d43621677 [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:0 sdb 8:16 \_ 3:0:0:0 sdf 8:80 create: 3600a0b80001327510000009a436215ec [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:1 sdc 8:32 \_ 3:0:0:1 sdg 8:96 create: 3600a0b80001327d800000070436216b3 [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:2 sdd 8:48 \_ 3:0:0:2 sdh 8:112 create: 3600a0b80001327510000009b4362163e [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:3 sde 8:64 \_ 3:0:0:3 sdi 8:128
devnode_blacklist { wwid SIBM-ESXSST336732LC____F3ET0EP0Q000072428BX1 }
multipath -F multipath -v2
multipath -F multipath -v2 create: 3600a0b80001327d80000006d43621677 [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:0 sdb 8:16 \_ 3:0:0:0 sdf 8:80 create: 3600a0b80001327510000009a436215ec [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:1 sdc 8:32 \_ 3:0:0:1 sdg 8:96 create: 3600a0b80001327d800000070436216b3 [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:2 sdd 8:48 \_ 3:0:0:2 sdh 8:112 create: 3600a0b80001327510000009b4362163e [size=12 GB][features="0"][hwhandler="0"] \_ round-robin 0 \_ 2:0:0:3 sde 8:64 \_ 3:0:0:3 sdi 8:128
Chapter 1. JBoss EAP Security Domains 1.1. About Security Domains Security domains are part of the JBoss EAP 6 security subsystem. All security configuration is now managed centrally, by the domain controller of a managed domain, or by the standalone server. A security domain consists of configurations for authentication, authorization, security mapping, and auditing. It implements Java Authentication and Authorization Service (JAAS) declarative security. Authentication refers to verifying the identity of a user. In security terminology, this user is referred to as a principal . Although authentication and authorization are different, many of the included authentication modules also handle authorization. Authorization is a process by which the server determines if an authenticated user has permission or privileges to access specific resources in the system or operation. Security mapping refers to the ability to add, modify, or delete information from a principal, role, or attribute before passing the information to your application. The auditing manager allows you to configure provider modules to control the way that security events are reported. If you use security domains, you can remove all specific security configuration from your application itself. This allows you to change security parameters centrally. One common scenario that benefits from this type of configuration structure is the process of moving applications between testing and production environments.

Commands:
Chapter 7. Using Hibernate with JBoss Data Virtualization 7.1. Configure Hibernate for Use with JBoss Data Virtualization Prerequisites You must have the JBoss Data Virtualization JDBC API client JAR file ( teiid-client.jar ) and the JBoss Data Virtualization hibernate dialect JAR file ( teiid-hibernate-dialect- VERSION .jar ) in Hibernate's classpath. These files are found in EAP_HOME /modules/system/layers/dv/org/jboss/teiid/client/main/ . These are required for the org.teiid.dialect.TeiidDialect , org.teiid.jdbc.TeiidDriver and org.teiid.jdbc.TeiidDataSource classes. Procedure 7.1. Configure Hibernate for Use with JBoss Data Virtualization Open the Hibernate configuration file Open the hibernate.cfg.xml file. Specify the JBoss Data Virtualization driver class Specify the JBoss Data Virtualization driver class in the connection.driver_class property: Set the Connection URL Specify the URL for the VDB in the connection.url property: Note Be sure to use a local connection if Hibernate is in the same VM as the application server. . Specify the dialect class Specify the JBoss Data Virtualization dialect class in the dialect property: Note Alternatively, the connection properties can be added to the hibernate.properties file instead of hibernate.cfg.xml : Note Since your VDBs will likely contain multiple source and view models with identical table names, you will need to fully qualify table names specified in Hibernate mapping files: For example:

Commands:
<property name="connection.driver_class"> org.teiid.jdbc.TeiidDriver </property>
<property name="connection.url"> jdbc:teiid:VDB-NAME@mm://HOST:POST;user=USERNAME;password=PASSWORD </property>
<property name="dialect"> org.teiid.dialect.TeiidDialect </property>
hibernate.connection.driver_class=org.teiid.jdbc.TeiidDriver hibernate.connection.url=jdbc:teiid:VDB-NAME@mm://HOST:PORT hibernate.connection.username=USERNAME hibernate.connection.password=PASSWORD hibernate.dialect=org.teiid.dialect.TeiidDialect
<class name="CLASSNAME" table="SOURCE/VIEW_MODEL_NAME.[SCHEMA_NAME.]TABLENAME"> </class>
<class name="org.teiid.example.Publisher" table="BOOKS.BOOKS.PUBLISHERS"> </class>
3.3. Editing an Image Builder blueprint with command-line interface This procedure describes how to edit an existing Image Builder blueprint in the command-line interface. Procedure 1. Save (export) the blueprint to a local text file: 2. Edit the BLUEPRINT-NAME.toml file with a text editor of your choice and make your changes. 3. Before finishing the edits, make sure the file is a valid blueprint: Remove this line, if present: Increase the version number. Remember that Image Builder blueprint versions must use the Semantic Versioning scheme. Note also that if you do not change the version, the patch component of version is increased automatically. Check if the contents are valid TOML specifications. See the TOML documentation for more information. Note TOML documentation is a community product and is not supported by Red Hat. You can report any issues with the tool at https://github.com/toml-lang/toml/issues 4. Save the file and close the editor. 5. Push (import) the blueprint back into Image Builder: Note that you must supply the file name including the .toml extension, while in other commands you use only the name of the blueprint. 6. To verify that the contents uploaded to Image Builder match your edits, list the contents of blueprint: 7. Check whether the components and versions listed in the blueprint and their dependencies are valid:

Commands:
composer-cli blueprints save BLUEPRINT-NAME
packages = []
composer-cli blueprints push BLUEPRINT-NAME.toml
composer-cli blueprints show BLUEPRINT-NAME
composer-cli blueprints depsolve BLUEPRINT-NAME
Chapter 30. Kernel libcgroup no longer truncates the values of cgroup subsystem parameters that are longer than 100 characters Previously, the internal representation of a value of any cgroup subsystem parameter was limited to have the length of 100 characters at maximum. Consequently, the libcgroup library truncated the values longer than 100 characters before writing them to a file representing matching cgroup subsystem parameter in the kernel. With this update, the maximal length of values of cgroup subsystem parameters in libcgroup has been extended to 4096 characters. As a result, libcgroup now handles values of cgroup subsystem parameters with any length correctly. (BZ#1549175) The mlx5 device no longer contains a firmware issue Previously, the mlx5 device contained a firmware issue, which caused that the link of mlx5 devices in certain situation dropped after rebooting a system. As a consequence, a message similar to the following was seen in the output of the dmesg command: The issue is fixed in the latest firmware of this device. Contact your hardware vendor for information on how to obtain and install the latest firmware for your mlx5 device. (BZ#1636930)

Commands:
mlx5_core 0000:af:00.0: Port module event[error]: module 0, Cable error, Bus stuck(I2C or data shorted)