mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Installing .NET 9.0 .NET 9.0 is included in the AppStream repositories for RHEL 9. The AppStream repositories are enabled by default on RHEL 9 systems. You can install the .NET 9.0 runtime with the latest 9.0 Software Development Kit (SDK). When a newer SDK becomes available for .NET 9.0, you can install it by running sudo dnf install . Prerequisites Installed and registered RHEL 9.10 with attached subscriptions. For more information, see Interactively installing RHEL from installation media . Procedure Install .NET 9.0 and all of its dependencies: Verification Verify the installation: The output returns the relevant information about the .NET installation and the environment.

Commands:
sudo dnf install dotnet-sdk-9.0 -y
dotnet --info
Chapter 10. Monitoring a high availability Red Hat Ceph Storage cluster When you deploy an overcloud with Red Hat Ceph Storage, Red Hat OpenStack Platform uses the ceph-mon monitor daemon to manage the Ceph cluster. Director deploys the daemon on all Controller nodes. 10.1. Checking Red Hat Ceph monitoring service status To check the status of the Red Hat Ceph Storage monitoring service, log in to a Controller node and run the service ceph status command. Procedure Log in to a Controller node and check that the Ceph Monitoring service is running: 10.2. Checking Red Hat Ceph monitoring configuration To check the configuration of the Red Hat Ceph Storage monitoring service, log in to a Controller node or a Red Hat Ceph node and open the /etc/ceph/ceph.conf file. Procedure Log in to a Controller nodes or on a Ceph node and open the /etc/ceph/ceph.conf file to view the monitoring configuration parameters: This example shows the following information: All three Controller nodes are configured to monitor the Red Hat Ceph Storage cluster with the mon_initial_members parameter. The 172.19.0.11/24 network is configured to provide a communication path between the Controller nodes and the Red Hat Ceph Storage nodes. The Red Hat Ceph Storage nodes are assigned to a separate network from the Controller nodes, and the IP addresses for the monitoring Controller nodes are 172.18.0.15 , 172.18.0.16 , and 172.18.0.17 . 10.3. Checking Red Hat Ceph node status To check the status of a specific Red Hat Ceph Storage node, log in to the node and run the ceph -s command. Procedure Log in to the Ceph node and run the ceph -s command: This example output shows that the health parameter value is HEALTH_OK , which indicates that the Ceph node is active and healthy. The output also shows three Ceph monitor services that are running on the three overcloud-controller nodes and the IP addresses and ports of the services. 10.4. Additional resources Red Hat Ceph product page

Commands:
sudo service ceph status === mon. overcloud-controller-0 === mon. overcloud-controller-0 : running {"version":"0.94.1"}
[global] osd_pool_default_pgp_num = 128 auth_service_required = cephx mon_initial_members = overcloud-controller-0 , overcloud-controller-1 , overcloud-controller-2 fsid = 8c835acc-6838-11e5-bb96-2cc260178a92 cluster_network = 172.19.0.11/24 auth_supported = cephx auth_cluster_required = cephx mon_host = 172.18.0.17,172.18.0.15,172.18.0.16 auth_client_required = cephx osd_pool_default_size = 3 osd_pool_default_pg_num = 128 public_network = 172.18.0.17/24
ceph -s cluster 8c835acc-6838-11e5-bb96-2cc260178a92 health HEALTH_OK monmap e1: 3 mons at { overcloud-controller-0 =172.18.0.17:6789/0, overcloud-controller-1 =172.18.0.15:6789/0, overcloud-controller-2 =172.18.0.16:6789/0} election epoch 152, quorum 0,1,2 overcloud-controller-1 , overcloud-controller-2 , overcloud-controller-0 osdmap e543: 6 osds: 6 up, 6 in pgmap v1736: 256 pgs, 4 pools, 0 bytes data, 0 objects 267 MB used, 119 GB / 119 GB avail 256 active+clean
Appendix A. About Service Interconnect documentation Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Revised on 2025-02-24 19:05:08 UTC

Commands:
5.287. rsync 5.287.1. RHBA-2012:0473 - rsync bug fix update An updated rsync package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The rsync tool is used to copy and synchronize files locally or across a network. The rsync works very fast because it uses delta encoding and sends only differences in files instead of whole files. The rsync is also used as a powerful mirroring tool. Bug Fixes BZ# 737539 When creating a sparse file that was zero blocks long, the "rsync --sparse" command did not properly truncate the sparse file at the end of the copy transaction. As a consequence, the file size was bigger than expected. With this update, the underlying source code has been modified to ensure proper truncating of such files. BZ# 804916 Previously, the rsync utility could terminate unexpectedly with the following error during a data transfer: This happened if the block size was exactly of the size of the CHUNK_SIZE constant. The output buffer was completely filled after calling the inflate() function for the first time, and it was therefore not possible to obtain remaining buffer output when calling inflate() the time. The Z_BUF_ERROR constant is now handled properly, and so prevents rsync from terminating in the described scenario. All users of rsync are advised to upgrade to this updated package, which fixes these bugs. 5.287.2. RHBA-2013:1501 - rsync bug fix update Updated rsync packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The rsync tool is used to copy and synchronize files locally or across a network. The rsync works very fast because it uses delta encoding and sends just differences in files instead of whole files. The rsync is also used as powerful mirroring tool. Bug Fix BZ# 1022357 Previously, the rsync tool did not check whether the inbuf variable is non-empty. As a consequence, rsync terminated unexpectedly while trying to do the required encoding in a loop. With this update, rsync checks whether inbuf is non-empty and no longer crashes in the described scenario. Users of rsync are advised to upgrade to these updated packages, which fix this bug.

Commands:
Inflate (token) returned -5
7.5.2. Defining Persistent Audit Rules and Controls in the /etc/audit/audit.rules File To define Audit rules that are persistent across reboots, you must include them in the /etc/audit/audit.rules file. This file uses the same auditctl command line syntax to specify the rules. Any empty lines or any text following a hash sign ( # ) is ignored. The auditctl command can also be used to read rules from a specified file with the -R option, for example: Defining Control Rules A file can contain only the following control rules that modify the behavior of the Audit system: -b , -D , -e , -f , and -r . For more information on these options, see the section called "Defining Control Rules" . Example 7.3. Control rules in audit.rules Defining File System and System Call Rules File system and system call rules are defined using the auditctl syntax. The examples in Section 7.5.1, "Defining Audit Rules with the auditctl Utility" can be represented with the following rules file: Example 7.4. File system and system call rules in audit.rules Preconfigured Rules Files In the /usr/share/doc/audit- version / directory, the audit package provides a set of pre-configured rules files according to various certification standards: nispom.rules - Audit rule configuration that meets the requirements specified in Chapter 8 of the National Industrial Security Program Operating Manual. capp.rules - Audit rule configuration that meets the requirements set by Controlled Access Protection Profile (CAPP), which is a part of the Common Criteria certification. lspp.rules - Audit rule configuration that meets the requirements set by Labeled Security Protection Profile (LSPP), which is a part of the Common Criteria certification. stig.rules - Audit rule configuration that meets the requirements set by Security Technical Implementation Guides (STIG). To use these configuration files, create a backup of your original /etc/audit/audit.rules file and copy the configuration file of your choice over the /etc/audit/audit.rules file:

Commands:
~]# auditctl -R /usr/share/doc/audit- version /stig.rules
Delete all previous rules -D Set buffer size -b 8192 Make the configuration immutable -- reboot is required to change audit rules -e 2 Panic when a failure occurs -f 2 Generate at most 100 audit messages per second -r 100
-w /etc/passwd -p wa -k passwd_changes -w /etc/selinux/ -p wa -k selinux_changes -w /sbin/insmod -p x -k module_insertion -a always,exit -F arch=b64 -S adjtimex -S settimeofday -k time_change -a always,exit -S unlink -S unlinkat -S rename -S renameat -F auid>=500 -F auid!=4294967295 -k delete
~]# cp /etc/audit/audit.rules /etc/audit/audit.rules_backup ~]# cp /usr/share/doc/audit- version /stig.rules /etc/audit/audit.rules
7.65. gd 7.65.1. RHBA-2012:1274 - gd bug fix update Updated gd packages that fix one bug is now available for Red Hat Enterprise Linux 6. The gd packages provide the gd graphics library. GD allows code to draw images as PNG or JPEG files. BZ#790400 Prior to this update, ,the gd graphics library handled inverted Y coordinates incorrectly, when changing the thickness of a line. As a consequence, lines with changed thickness were drawn incorrectly. This update modifies the underlying code to draw lines with changed thickness correctly. All users of gd are advised to upgrade to these updated packages, which fix this bug.

Commands:
Overcloud Parameters Red Hat OpenStack Platform 16.2 Parameters for customizing the core template collection for a Red Hat OpenStack Platform overcloud OpenStack Documentation Team rhos-docs@redhat.com Abstract This guide lists common parameters that are used in the deployment of OpenStack using the Orchestration service (heat). This guide is not a comprehensive resource, and not all parameters that are listed can be used in a supported configuration. The following parameters and definitions are extracted from source code, and provided here as reference only.

Commands:
B.96.3. RHSA-2011:0311 - Critical: thunderbird security update An updated thunderbird package that fixes several security issues is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Mozilla Thunderbird is a standalone mail and newsgroup client. CVE-2010-1585 , CVE-2011-0053 , CVE-2011-0062 Several flaws were found in the processing of malformed HTML content. Malicious HTML content could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. CVE-2011-0061 A flaw was found in the way Thunderbird handled malformed JPEG images. An HTML mail message containing a malicious JPEG image could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. All Thunderbird users should upgrade to this updated package, which resolves these issues. All running instances of Thunderbird must be restarted for the update to take effect.

Commands:
Chapter 1. Installation Overview The self-hosted engine installation uses Ansible and the RHV-M Appliance (a pre-configured Manager virtual machine image) to automate the following tasks: Configuring the first self-hosted engine node Installing a Red Hat Enterprise Linux virtual machine on that node Installing and configuring the Red Hat Virtualization Manager on that virtual machine Configuring the self-hosted engine storage domain Note The RHV-M Appliance is only used during installation. It is not used to upgrade the Manager. Installing a self-hosted engine environment involves the following steps: Prepare storage to use for the self-hosted engine storage domain and for standard storage domains. You can use one of the following storage types: NFS iSCSI Fibre Channel (FCP) Red Hat Gluster Storage Install a deployment host to run the installation on. This host will become the first self-hosted engine node. You can use either host type: Red Hat Virtualization Host Red Hat Enterprise Linux Install and configure the Red Hat Virtualization Manager: Enabling and configuring the firewall Install the self-hosted engine using the hosted-engine --deploy command on the deployment host. Register the Manager with the Content Delivery Network and enable the Red Hat Virtualization Manager repositories. Connect to the Administration Portal to add hosts and storage domains. Add more self-hosted engine nodes and standard hosts to the Manager. Self-hosted engine nodes can run the Manager virtual machine and other virtual machines. Standard hosts can run all other virtual machines, but not the Manager virtual machine. Use either host type, or both: Red Hat Virtualization Host Red Hat Enterprise Linux Add hosts to the Manager as self-hosted engine nodes. Add hosts to the Manager as standard hosts. Add more storage domains to the Manager. The self-hosted engine storage domain is not recommended for use by anything other than the Manager virtual machine. If you want to host any databases or services on a server separate from the Manager, you can migrate them after the installation is complete. Important Keep the environment up to date. See How do I update my Red Hat Virtualization system? for more information. Since bug fixes for known issues are frequently released, use scheduled tasks to update the hosts and the Manager.

Commands:
function::probefunc Name function::probefunc - Return the probe point's function name, if known. Synopsis Arguments None General Syntax probefunc: string Description This function returns the name of the function being probed. It will do this based on the probe point string as returned by pp . Please note this function is deprecated, please use symname and/or usymname . This function might return a function name based on the current address if the probe point context couldn't be parsed.

Commands:
function probefunc:string()
Chapter 1. About OpenShift Virtualization Learn about OpenShift Virtualization's capabilities and support scope. 1.1. What you can do with OpenShift Virtualization OpenShift Virtualization is an add-on to OpenShift Container Platform that allows you to run and manage virtual machine workloads alongside container workloads. OpenShift Virtualization adds new objects into your OpenShift Container Platform cluster by using Kubernetes custom resources to enable virtualization tasks. These tasks include: Creating and managing Linux and Windows virtual machines Connecting to virtual machines through a variety of consoles and CLI tools Importing and cloning existing virtual machines Managing network interface controllers and storage disks attached to virtual machines Live migrating virtual machines between nodes An enhanced web console provides a graphical portal to manage these virtualized resources alongside the OpenShift Container Platform cluster containers and infrastructure. OpenShift Virtualization is designed and tested to work well with Red Hat OpenShift Data Foundation features. Important When you deploy OpenShift Virtualization with OpenShift Data Foundation, you must create a dedicated storage class for Windows virtual machine disks. See Optimizing ODF PersistentVolumes for Windows VMs for details. You can use OpenShift Virtualization with the OVN-Kubernetes , OpenShift SDN , or one of the other certified network plugins listed in Certified OpenShift CNI Plug-ins . 1.1.1. OpenShift Virtualization supported cluster version OpenShift Virtualization 4.12 is supported for use on OpenShift Container Platform 4.12 clusters. To use the latest z-stream release of OpenShift Virtualization, you must first upgrade to the latest version of OpenShift Container Platform. 1.2. Single-node OpenShift differences You can install OpenShift Virtualization on a single-node cluster. When provisioning a single-node OpenShift cluster with the assisted installer, preconfigured persistent storage is deployed automatically. In OpenShift Virtualization 4.10 and 4.11, the HostPath Provisioner (HPP) is automatically installed. In OpenShift Virtualization 4.12, the OpenShift Data Foundation Logical Volume Manager Operator is the provided out-of-the-box storage solution. You can also manually deploy using the HPP. Note Single-node OpenShift does not support high availability. Be aware of the following differences in functionality from a multiple-node cluster: Pod disruption budgets are not supported. Live migration is not supported. Due to differences in storage behavior, some virtual machine templates are incompatible with single-node OpenShift. To ensure compatibility, templates or virtual machines that use data volumes or storage profiles must not have the eviction strategy set. 1.3. Additional resources About single-node OpenShift Assisted installer Hostpath Provisioner (HPP) OpenShift Container Platform Data Foundation Logical Volume Manager Operator Pod disruption budgets Live migration Eviction strategy Supported limits for OpenShift Virtualization 4.x

Commands:
7.150. pacemaker 7.150.1. RHSA-2015:1424 - Moderate: pacemaker security and bug fix update Updated pacemaker packages that fix one security issue and several bugs are now available for Red Hat Enterprise Linux 6. Red Hat Product Security 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 from the CVE link in the References section. The Pacemaker Resource Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Security Fix CVE-2015-1867 A flaw was found in the way pacemaker, a cluster resource manager, evaluated added nodes in certain situations. A user with read-only access could potentially assign any other existing roles to themselves and then add privileges to other users as well. Bug Fixes BZ# 1198638 Due to a race condition, nodes that gracefully shut down occasionally had difficulty rejoining the cluster. As a consequence, nodes could come online and be shut down again immediately by the cluster. This bug has been fixed, and the "shutdown" attribute is now cleared properly. BZ# 1205292 Prior to this update, the pacemaker utility caused an unexpected termination of the attrd daemon after a system update to Red Hat Enterprise Linux 6.6. The bug has been fixed so that attrd no longer crashes when pacemaker starts. BZ# 1207621 Previously, the access control list (ACL) of the pacemaker utility allowed a role assignment to the Cluster Information Base (CIB) with a read-only permission. With this update, ACL is enforced and can no longer be bypassed by the user without the write permission, thus fixing this bug. BZ# 1208896 Prior to this update, the ClusterMon (crm_mon) utility did not trigger an external agent script with the "-E" parameter to monitor the Cluster Information Base (CIB) when the pacemaker utility was used. A patch has been provided to fix this bug, and crm_mon now calls the agent script when the "-E" parameter is used. Users of pacemaker are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

Commands:
7.36. dejavu-fonts 7.36.1. RHBA-2015:1327 - dejavu-fonts bug fix and enhancement update Updated dejavu-fonts packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The DejaVu fonts are a font family based on the Vera Fonts. Its purpose is to provide a wider range of characters while maintaining the original look and feel through the process of collaborative development. Note The dejavu-fonts packages have been upgraded to upstream version 2.33, which provides a number of bug fixes and enhancements over the version. Notably, this adds a number of new characters and symbols to the supported fonts. (BZ# 1060882 ) Users of dejavu-fonts are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Introduction Red Hat Satellite provides a Representational State Transfer (REST) API. The API provides software developers and system administrators with control over their Red Hat Satellite environment outside of the standard web interface. The REST API is useful for developers and administrators who aim to integrate the functionality of Red Hat Satellite with custom scripts or external applications that access the API over HTTP. 1.1. Overview of the Red Hat Satellite API The benefits of using the REST API are: Broad client support - any programming language, framework, or system with support for HTTP protocol can use the API. Self-descriptive - client applications require minimal knowledge of the Red Hat Satellite infrastructure because a user discovers many details at runtime. Resource-based model - the resource-based REST model provides a natural way to manage a virtualization platform. You can use the REST API to perform the following tasks: Integrate with enterprise IT systems. Integrate with third-party applications. Perform automated maintenance or error checking tasks. Automate repetitive tasks with scripts. As you prepare to upgrade Satellite Server, ensure that any scripts you use that contain Satellite API commands are up to date. API commands differ between versions of Satellite. 1.2. Satellite API compared to Hammer CLI tool For many tasks, you can use both Hammer and Satellite API. You can use Hammer as a human-friendly interface to Satellite API. For example, to test responses to API calls before applying them in a script, use the --debug option to inspect API calls that Hammer issues: hammer --debug organization list . In the background, each Hammer command first establishes a binding to the API and then sends a request. This can have performance implications when executing a large number of Hammer commands in sequence. In contrast, scripts that use API commands communicate directly with the Satellite API. Note that you must manually update scripts that use API commands, while Hammer automatically reflects changes in the API. For more information, see the Hammer CLI Guide .

Commands: