mtpti5iD/redhat-docs_dataset huggingface dataset:
11.2. Adding Services and Certificates for Services While services can use keytabs, some services require certificates for access. In that case, a service can be added (or modified) to include a certificate with its service entry. 11.2.1. Adding Services and Certificates from the Web UI Open the Identity tab, and select the Services subtab. Click the Add link at the top of the services list. Select the service type from the drop-down menu, and give it a name. Select the hostname of the IdM host on which the service is running. The hostname is used to construct the full service principal name. Click the Add and Edit button to go directly to the service entry page. Scroll to the bottom of the page, to the Service Certificate section. Click the New Certificate button to create the service certificate. 11.2.2. Adding Services and Certificates from the Command Line Create the service principal. The service is recognized through a name like service/FQDN : For example: USD ipa service-add HTTP/server.example.com ------------------------------------------------------- Added service "HTTP/server.example.com@EXAMPLE.COM" ------------------------------------------------------- Principal: HTTP/server.example.com@EXAMPLE.COM Managed by: ipaserver.example.com Create a certificate for the service. Be sure to copy the keytab to the appropriate directory for the service. For example: Note Use the --add option to create the service automatically when requesting the certificate. Alternatively, use the getcert command, which creates and manages the certificate through certmonger . The options are described more in Section B.1, "Requesting a Certificate with certmonger" .

Commands:
[jsmith@ipaserver ~]USD kinit admin [jsmith@ipaserver ~]USD ipa service-add serviceName/hostname
ipa service-add HTTP/server.example.com ------------------------------------------------------- Added service "HTTP/server.example.com@EXAMPLE.COM" ------------------------------------------------------- Principal: HTTP/server.example.com@EXAMPLE.COM Managed by: ipaserver.example.com
ipa cert-request --principal=HTTP/web.example.com example.csr
ipa-getcert request -d /etc/httpd/alias -n Server-Cert -K HTTP/client1.example.com -N 'CN=client1.example.com,O=EXAMPLE.COM'
31.3.3. Firewall Considerations If you are performing the installation where the VNC viewer system is a workstation on a different subnet from the target system, you may run in to network routing problems. VNC works fine so long as your viewer system has a route to the target system and ports 5900 and 5901 are open. If your environment has a firewall, make sure ports 5900 and 5901 are open between your workstation and the target system. In addition to passing the vnc boot parameter, you may also want to pass the vncpassword parameter in these scenarios. While the password is sent in plain text over the network, it does provide an extra step before a viewer can connect to a system. Once the viewer connects to the target system over VNC, no other connections are permitted. These limitations are usually sufficient for installation purposes. Important Be sure to use a temporary password for the vncpassword option. It should not be a password you use on any systems, especially a real root password. If you continue to have trouble, consider using the vncconnect parameter. In this mode of operation, you start the viewer on your system first telling it to listen for an incoming connection. Pass vncconnect= HOST at the boot prompt and the installer will attempt to connect to the specified HOST (either a hostname or IP address).

Commands:
Chapter 11. Red Hat Fuse and Red Hat Process Automation Manager Red Hat Fuse is a distributed, cloud-native integration platform that is part of an agile integration solution. Its distributed approach enables teams to deploy integrated services where required. Fuse has the flexibility to service diverse users, including integration experts, application developers, and business users, each with their own choice of deployment, architecture, and tooling. The API-centric, container-based architecture decouples services so they can be created, extended, and deployed independently. The result is an integration solution that supports collaboration across the enterprise. Red Hat Process Automation Manager is the Red Hat platform for creating business automation applications and microservices. It enables enterprise business and IT users to document, simulate, manage, automate, and monitor business processes and policies. Red Hat Process Automation Manager is designed to empower business and IT users to collaborate more effectively, so business applications can be changed easily and quickly. You can install Red Hat Fuse on the Apache Karaf container platform and then install and configure Red Hat Process Automation Manager in that container. You can also install Red Hat Fuse on a separate instance of Red Hat JBoss Enterprise Application Platform and integrate it with Red Hat Process Automation Manager. The kie-camel module provides integration between Red Hat Fuse and Red Hat Process Automation Manager. Important For the version of Red Hat Fuse that Red Hat Process Automation Manager 7.13 supports, see Red Hat Process Automation Manager 7 Supported Configurations . Note You can install Red Hat Fuse on Spring Boot. Red Hat Process Automation Manager provides no special integration for this scenario. You can use the kie-server-client library in an application running on Red Hat Fuse on Spring Boot to enable communication with Red Hat Process Automation Manager services running on a KIE Server. For instructions about using the kie-server-client library, see Interacting with Red Hat Process Automation Manager using KIE APIs .

Commands:
Chapter 3. Internal storage services Red Hat OpenShift Data Foundation service is available for consumption internally to the Red Hat OpenShift Container Platform that runs on the following infrastructure: Amazon Web Services (AWS) Bare metal VMware vSphere Microsoft Azure Google Cloud Red Hat OpenStack 13 or higher (installer-provisioned infrastructure) [Technology Preview] IBM Power IBM Z and IBM(R) LinuxONE ROSA with hosted control planes (HCP) [Technology Preview] Creation of an internal cluster resource results in the internal provisioning of the OpenShift Data Foundation base services, and makes additional storage classes available to the applications.

Commands:
4.9.3. Sorting LVM Reports Normally the entire output of the lvs , vgs , or pvs command has to be generated and stored internally before it can be sorted and columns aligned correctly. You can specify the --unbuffered argument to display unsorted output as soon as it is generated. To specify an alternative ordered list of columns to sort on, use the -O argument of any of the reporting commands. It is not necessary to include these fields within the output itself. The following example shows the output of the pvs command that displays the physical volume name, size, and free space. The following example shows the same output, sorted by the free space field. The following example shows that you do not need to display the field on which you are sorting. To display a reverse sort, precede a field you specify after the -O argument with the - character.

Commands:
pvs -o pv_name,pv_size,pv_free PV PSize PFree /dev/sdb1 17.14G 17.14G /dev/sdc1 17.14G 17.09G /dev/sdd1 17.14G 17.14G
pvs -o pv_name,pv_size,pv_free -O pv_free PV PSize PFree /dev/sdc1 17.14G 17.09G /dev/sdd1 17.14G 17.14G /dev/sdb1 17.14G 17.14G
pvs -o pv_name,pv_size -O pv_free PV PSize /dev/sdc1 17.14G /dev/sdd1 17.14G /dev/sdb1 17.14G
pvs -o pv_name,pv_size,pv_free -O -pv_free PV PSize PFree /dev/sdd1 17.14G 17.14G /dev/sdb1 17.14G 17.14G /dev/sdc1 17.14G 17.09G
B.40. libcap-ng B.40.1. RHBA-2010:0906 - libcap-ng bug fix update Updated libcap-ng packages that fix a bug are now available for Red Hat Enterprise Linux 6. The libcap-ng library is designed to make programming with POSIX capabilities easier. It is shipped with utilities to analyze the POSIX capabilities of all running applications, as well as tools to set the file system-based capabilities. Bug Fix BZ# 650131 Previously, when listing the file system based capabilities of a single file with the "filecap" utility, it would terminate with a segmentation fault. This error has been fixed, and "filecap" no longer crashes when attempting to list the capabilities of a single file. Users are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 3. Red Hat build of OpenJDK 11.0.14.1 release notes Review the following release notes to understand changes from this Red Hat build of OpenJDK 11.0.14 patch release: 3.1. Resolved https://google.com connection issue The Red Hat build of OpenJDK 11.0.14.1 release resolves an issue that was identified when using the Java HTTP client, java.net.HTTPClient , to connect to the https://google.com URL. This issue persisted on the Red Hat build of OpenJDK build for Microsoft Windows and on the Red Hat build of OpenJDK build for RHEL. The initial Red Hat build of OpenJDK 11.0.14 release contained a regression that was introduced by improvements to the HTTP client. This regression caused both the :authority and the Host header fields to be sent in HTTP/2 requests, which are rejected by some HTTP servers, such as Google's server. When you attempted to establish this connection, you would receive an exception message. This exception message would indicate that the Java HTTP client could not successfully communicate by using the HTTP/2 protocol. Example of an exception message when attempting to connect to https://google.com with java.net.HTTPClient java.util.concurrent.ExecutionException: java.io.IOException: Received RST_STREAM: Protocol error The Red Hat build of OpenJDK 11.0.14.1 release resolves the issue by reverting to the original behavior of only setting the :authority header field to be sent in an HTTP/2 request. For more information about this issue and how it was resolved, see JDK-8218546 and see the advisories related to the Red Hat build of OpenJDK 11.0.14.1 release. 3.2. Advisories related to the Red Hat build of OpenJDK 11.0.14.1 release The following advisories have been issued to bugfixes and CVE fixes included in this release: RHBA-2022:0732 RHBA-2022:0733

Commands:
java.util.concurrent.ExecutionException: java.io.IOException: Received RST_STREAM: Protocol error
10.3. Red Hat Enterprise Linux hosts You can use a Red Hat Enterprise Linux 7 installation on capable hardware as a host. Red Hat Virtualization supports hosts running Red Hat Enterprise Linux 7 Server AMD64/Intel 64 version with Intel VT or AMD-V extensions. To use your Red Hat Enterprise Linux machine as a host, you must also attach the Red Hat Enterprise Linux Server and Red Hat Virtualization subscriptions. Adding a host can take some time, as the following steps are completed by the platform: virtualization checks, installation of packages, and the creation of a bridge. Use the details view to monitor the process as the host and management system establish a connection. Optionally, you can install a Cockpit web interface for monitoring the host's resources and performing administrative tasks. The Cockpit web interface provides a graphical user interface for tasks that are performed before the host is added to the Red Hat Virtualization Manager, such as configuring networking and deploying a self-hosted engine, and can also be used to run terminal commands via the Terminal sub-tab. Important Third-party watchdogs should not be installed on Red Hat Enterprise Linux hosts, as they can interfere with the watchdog daemon provided by VDSM.

Commands:
3.10. Network Labels Network labels can be used to greatly simplify several administrative tasks associated with creating and administering logical networks and associating those logical networks with physical host network interfaces and bonds. A network label is a plain text, human readable label that can be attached to a logical network or a physical host network interface. There is no strict limit on the length of label, but you must use a combination of lowercase and uppercase letters, underscores and hyphens; no spaces or special characters are allowed. Attaching a label to a logical network or physical host network interface creates an association with other logical networks or physical host network interfaces to which the same label has been attached, as follows: Network Label Associations When you attach a label to a logical network, that logical network will be automatically associated with any physical host network interfaces with the given label. When you attach a label to a physical host network interface, any logical networks with the given label will be automatically associated with that physical host network interface. Changing the label attached to a logical network or physical host network interface acts in the same way as removing a label and adding a new label. The association between related logical networks or physical host network interfaces is updated. Network Labels and Clusters When a labeled logical network is added to a cluster and there is a physical host network interface in that cluster with the same label, the logical network is automatically added to that physical host network interface. When a labeled logical network is detached from a cluster and there is a physical host network interface in that cluster with the same label, the logical network is automatically detached from that physical host network interface. Network Labels and Logical Networks With Roles When a labeled logical network is assigned to act as a display network or migration network, that logical network is then configured on the physical host network interface using DHCP so that the logical network can be assigned an IP address. Setting a label on a role network (for instance, "a migration network" or "a display network") causes a mass deployment of that network on all hosts. Such mass additions of networks are achieved through the use of DHCP. This method of mass deployment was chosen over a method of typing in static addresses, because of the unscalable nature of the task of typing in many static IP addresses.

Commands:
18.12.11.4. Pre-existing network filters The following is a list of example network filters that are automatically installed with libvirt: Table 18.15. ICMPv6 protocol types Command Name Description no-arp-spoofing Prevents a guest virtual machine from spoofing ARP traffic; this filter only allows ARP request and reply messages and enforces that those packets contain the MAC and IP addresses of the guest virtual machine. allow-dhcp Allows a guest virtual machine to request an IP address via DHCP (from any DHCP server) allow-dhcp-server Allows a guest virtual machine to request an IP address from a specified DHCP server. The dotted decimal IP address of the DHCP server must be provided in a reference to this filter. The name of the variable must be DHCPSERVER . no-ip-spoofing Prevents a guest virtual machine from sending IP packets with a source IP address different from the one inside the packet. no-ip-multicast Prevents a guest virtual machine from sending IP multicast packets. clean-traffic Prevents MAC, IP and ARP spoofing. This filter references several other filters as building blocks. These filters are only building blocks and require a combination with other filters to provide useful network traffic filtering. The most used one in the above list is the clean-traffic filter. This filter itself can for example be combined with the no-ip-multicast filter to prevent virtual machines from sending IP multicast traffic on top of the prevention of packet spoofing.

Commands:
Appendix A. Component Versions This appendix is a list of components and their versions in the Red Hat Enterprise Linux 6.9 release. Table A.1. Component Versions Component Version Kernel 2.6.32-696 QLogic qla2xxx driver 8.07.00.26.06.8-k QLogic ql2xxx firmware ql2100-firmware-1.19.38-3.1 ql2200-firmware-2.02.08-3.1 ql23xx-firmware-3.03.27-3.1 ql2400-firmware-7.03.00-1 ql2500-firmware-7.03.00-1 Emulex lpfc driver 0:11.0.0.5 iSCSI initiator utils iscsi-initiator-utils-6.2.0.873-26 DM-Multipath device-mapper-multipath-0.4.9-100 LVM lvm2-2.02.143-12

Commands:
5.45. dash 5.45.1. RHBA-2012:1381 - dash bug fix update Updated dash packages that fix one bug are now available for Red Hat Enterprise Linux 6. The dash packages provide the POSIX-compliant Debian Almquist shell intended for small media like floppy disks. Bug Fix BZ# 706147 Prior to this update, the dash shell was not an allowed login shell. As a consequence, users could not log in using the dash shell. This update adds the dash to the /etc/shells list of allowed login shells when installing or upgrading dash package and removes it from the list when uninstalling the package. Now, users can login using the dash shell. All users of dash are advised to upgrade to these updated packages, which fix this bug.

Commands:
B.23. freetype B.23.1. RHSA-2010:0864 - Important: freetype security update Updated freetype packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. 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. FreeType is a free, high-quality, portable font engine that can open and manage font files. It also loads, hints, and renders individual glyphs efficiently. These packages provide the FreeType 2 font engine. CVE-2010-2805 , CVE-2010-3311 It was found that the FreeType font rendering engine improperly validated certain position values when processing input streams. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. CVE-2010-2808 A stack-based buffer overflow flaw was found in the way the FreeType font rendering engine processed some PostScript Type 1 fonts. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. CVE-2010-2806 An array index error was found in the way the FreeType font rendering engine processed certain PostScript Type 42 font files. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Note: All of the issues in this erratum only affect the FreeType 2 font engine. Users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. The X server must be restarted (log out, then log back in) for this update to take effect.

Commands:
5.158. libtar 5.158.1. RHBA-2012:0462 - libtar bug fix update Updated libtar packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libtar package contains a C library for manipulating tar archives. The library supports both the strict POSIX tar format and many of the commonly used GNU extensions. Bug Fix BZ# 729009 Previously, the build system configuration files included in the libtar package were incompatible with the way the rpmbuild tool extracts debugging information from the binaries installed to the rpm build root during the build of a package. As a consequence, the libtar-debuginfo package did not contain debugging information. A patch has been applied to address this issue, and the libtar-debuginfo package now contains the appropriate content. All users of libtar are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. About networking Red Hat OpenShift Networking is an ecosystem of features, plugins and advanced networking capabilities that extend Kubernetes networking with the advanced networking-related features that your cluster needs to manage its network traffic for one or multiple hybrid clusters. This ecosystem of networking capabilities integrates ingress, egress, load balancing, high-performance throughput, security, inter- and intra-cluster traffic management and provides role-based observability tooling to reduce its natural complexities. Note OpenShift SDN CNI is deprecated as of OpenShift Container Platform 4.14. As of OpenShift Container Platform 4.15, the network plugin is not an option for new installations. In a subsequent future release, the OpenShift SDN network plugin is planned to be removed and no longer supported. Red Hat will provide bug fixes and support for this feature until it is removed, but this feature will no longer receive enhancements. As an alternative to OpenShift SDN CNI, you can use OVN Kubernetes CNI instead. For more information, see OpenShift SDN CNI removal . The following list highlights some of the most commonly used Red Hat OpenShift Networking features available on your cluster: Primary cluster network provided by either of the following Container Network Interface (CNI) plugins: OVN-Kubernetes network plugin , the default plugin OpenShift SDN network plugin Certified 3rd-party alternative primary network plugins Cluster Network Operator for network plugin management Ingress Operator for TLS encrypted web traffic DNS Operator for name assignment MetalLB Operator for traffic load balancing on bare metal clusters IP failover support for high-availability Additional hardware network support through multiple CNI plugins, including for macvlan, ipvlan, and SR-IOV hardware networks IPv4, IPv6, and dual stack addressing Hybrid Linux-Windows host clusters for Windows-based workloads Red Hat OpenShift Service Mesh for discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring of services Single-node OpenShift Network Observability Operator for network debugging and insights Submariner for inter-cluster networking Red Hat Service Interconnect for layer 7 inter-cluster networking

Commands: