mtpti5iD/redhat-docs_dataset huggingface dataset:
15.2. Rolling Upgrades Using REST The following procedure outlines using Red Hat JBoss Data Grid installations as a remote grid using the REST protocol. This procedure applies to rolling upgrades for the grid, not the client application. Procedure 15.1. Perform Rolling Upgrades Using REST In the instructions, the Source Cluster refers to the old cluster that is currently in use and the Target Cluster refers to the destination cluster for our data. Configure the Target Cluster Use either different network settings or a different JGroups cluster name to set the Target Cluster (consisting of nodes with new JBoss Data Grid) apart from the Source Cluster. For each cache, configure a RestCacheStore with the following settings: Ensure that the host and port values point to the Source Cluster. Ensure that the path value points to the Source Cluster's REST endpoint. Start the Target Cluster Start the Target Cluster's nodes. Configure each client to point to the Target Cluster instead of the Source Cluster. Eventually, the Target Cluster handles all requests instead of the Source Cluster. The Target Cluster then lazily loads data from the Source Cluster on demand using the RestCacheStore . Do not dump the Key Set during REST Rolling Upgrades The REST Rolling Upgrades use case is designed to fetch all the data from the Source Cluster without using the recordKnownGlobalKeyset operation. Warning Do not invoke the recordKnownGlobalKeyset operation for REST Rolling Upgrades. If you invoke this operation, it will cause data corruption and REST Rolling Upgrades will not complete successfully. Fetch the Remaining Data The Target Cluster must fetch all the remaining data from the Source Cluster. This is done either using JMX or the CLI as follows: Using JMX Invoke the synchronizeData operation with the rest parameter specified on the RollingUpgradeManager MBean on the Target Cluster for all caches to be migrated. Using the CLI Run the upgrade --synchronize=rest on the Target Cluster for all caches to be migrated. Optionally, use the --all switch to synchronize all caches in the cluster. Disable the RestCacheStore Disable the RestCacheStore on the Target Cluster using either JMX or the CLI as follows: Using JMX Invoke the disconnectSource operation with the rest parameter specified on the RollingUpgradeManager MBean on the Target Cluster. Using the CLI Run the upgrade --disconnectsource=rest command on the Target Cluster. Optionally, use the --all switch to disconnect all caches in the cluster. Result Migration to the Target Cluster is complete. The Source Cluster can now be decommissioned. Report a bug

Commands:
10.5.22. Directory <Directory /path/to/directory> and </Directory> tags create a container used to enclose a group of configuration directives which apply only to a specific directory and its subdirectories. Any directive which is applicable to a directory may be used within Directory tags. By default, very restrictive parameters are applied to the root directory ( / ), using the Options (refer to Section 10.5.23, " Options " ) and AllowOverride (refer to Section 10.5.24, " AllowOverride " ) directives. Under this configuration, any directory on the system which needs more permissive settings has to be explicitly given those settings. In the default configuration, another Directory container is configured for the DocumentRoot which assigns less rigid parameters to the directory tree so that the Apache HTTP Server can access the files residing there. The Directory container can be also be used to configure additional cgi-bin directories for server-side applications outside of the directory specified in the ScriptAlias directive (refer to Section 10.5.41, " ScriptAlias " for more information). To accomplish this, the Directory container must set the ExecCGI option for that directory. For example, if CGI scripts are located in /home/my_cgi_directory , add the following Directory container to the httpd.conf file: , the AddHandler directive must be uncommented to identify files with the .cgi extension as CGI scripts. Refer to Section 10.5.56, " AddHandler " for instructions on setting AddHandler . For this to work, permissions for CGI scripts, and the entire path to the scripts, must be set to 0755.

Commands:
<Directory /home/my_cgi_directory> Options +ExecCGI </Directory>
4.35. crash 4.35.1. RHBA-2011:1648 - crash bug fix and enhancement update An updated crash package that fixes various bugs and adds several enhancements is now available for Red Hat Enterprise Linux 6. The crash package provides a self-contained tool that can be used to investigate live systems, and kernel core dumps created from the netdump, diskdump, kdump, and Xen/KVM "virsh dump" facilities from Red Hat Enterprise Linux. BZ# 710193 The crash package has been upgraded to upstream version 5.1.8, which provides a number of enhancements and bug fixes over the version. Bug Fixes BZ# 705142 Previously, compressed kdump dump files were handled incorrectly on AMD64 and Intel 64 architectures if a system contained more than 454 CPUs. In such a case, the crash session terminated during initialization with the "crash: compressed kdump: invalid nr_cpus value: [cpus]" error message. A patch has been provided to address this issue, and the compressed dump files are now handled properly, thus fixing this bug. BZ# 716931 When the first chunk of physical memory on a system was assigned to NUMA (Non-Uniform Memory Architecture) node 1 (typically it is assigned to NUMA node 0), the "kmem -s" or "kmem -S" command incorrectly showed all cache blocks allocated by the slab allocator as empty. This bug has been fixed, and the kmem command now shows populated kmem_cache slab data correctly. BZ# 712214 In a rare scenario, a non-crashing CPU received a shutdown NMI (non-maskable interrupt) immediately after receiving an interrupt from another source. Because the IRQ entry-point symbols "IRQ0x00_interrupt" through "IRQ0x##_interrupt" no longer existed, the bt command terminated with the "bt: cannot transition from exception stack to current process stack" error message on AMD64 and Intel 64 architectures. This bug has been fixed, and backtrace now properly transitions from the NMI stack back to the interrupted process stack. Enhancements BZ# 695413 The crash.8 man page and the associated built-in "crash -h" output have been re-written. The crash.8 man page now clarifies the required invocation options, adds all of the rarely-used command line options that have proliferated over the years, and updates the ENVIRONMENT variables section. The "crash -h" output now closely mimics the relevant parts of the crash.8 man page. BZ# 703467 With this update, the new "--osrelease [dump_file]" command line option that displays the OSRELEASE vmcoreinfo string from a kdump dump file has been added. Users of crash are advised to upgrade to this updated package which fixes these bugs and adds these enhancements.

Commands:
Chapter 1. Installing the JBoss Web Server collection As a first step toward automating deployments of Red Hat JBoss Web Server by using Ansible, you must download and install the JBoss Web Server collection from Ansible automation hub . The JBoss Web Server collection is named redhat.jws in Ansible automation hub. Before you install the JBoss Web Server collection, you must ensure that your system complies with certain prerequisites. You must install the JBoss Web Server collection on an Ansible control node in your system. For more information about any prerequisites and installing the collection, see Installing the JBoss Web Server collection .

Commands:
Chapter 27. Network Driver Updates The ixgbevf driver has been updated to version 2.12.1-k. The ixgbe driver has been updated to version 4.2.1-k. The mlx5_core driver has been updated to version 3.0-1. The 3c59x network card driver has been updated to the latest upstream version. The rds (Reliable Datagram Sockets) driver has been updated to the latest upstream version. The be2iscsi driver has been updated to version 10.4.272.1r, which is the equivalent of upstream version 10.6.0.1. The fnic driver has been updated to version 1.6.0.17a. The ocrdma driver has been updated to the latest upstream version. The ibmveth (IBM Virtual Ethernet) driver has been updated to version 1.05. The hfi driver has been updated to the latest upstream version. The ocrdma network hardware driver has been rebased to upstream version 4.1. The bna driver has been updated to version 3.2.25.1r. The i40e driver has been updated to version 1.4.7-k. Note that only the Ethernet functionalities of this driver are supported in Red Hat Enterprise Linux 6.8. The i40evf driver has been updated to version 1.4.3. The enic driver has been updated to version 2.3.0.12. The be2net driver has been updated to version 10.6.0.3r. The bnx2x driver has been updated to version 1.712.30-0. The bnx2 driver has been updated to version 2.2.6. The tg3 driver has been updated to version 3.137. The e100 driver has been updated to version 3.5.24-k2-NAPI. The e1000 driver has been updated to version 7.3.21-k8-NAPI. The e1000e driver has been updated to version 3.2.6-k. The bfa driver has been updated to upstream version 3.2.25. The wireless drivers, brcmfmac , rtlwifi , rt2x00 , iwlwifi , b43 , iwlegacy , carl9170 , ath5k , and ath9k , have been updated to the upstream kernel version 4.3.6.

Commands:
8.122. libsoup 8.122.1. RHBA-2014:1561 - libsoup bug fix and enhancement update Updated libsoup packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libsoup packages provide an HTTP client and server library for GNOME. Note The libsoup packages have been upgraded to upstream version 2.34.0, which provides a number of bug fixes and enhancements over the version. (BZ# 869322 , BZ# 1101399 ) Users of libsoup are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 6. Updating a system You can send an update to a system through the dashboard application. For that, you can use the Update button in the dashboard to add the latest package version update to the image. You must use the following procedure to perform the update. Warning Currently, there is no support for updating an Edge system by using the CLI. You can only update your Edge systems by using the Red Hat Hybrid Cloud Console. See How to start the upgrade process of an Edge Management deployed system . Prerequisite You must have a Red Hat Hybrid Cloud Console account. A system is built from an image and registered with the Red Hat Hybrid Cloud Console. An update to that image has been built. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Systems . Click the More options icon (...) for the system you want to update. Click Update Image . The Status column for the system will say Update available if your image update was successful. On the Update page, select an image version. If there are two or more newer image updates for your system, you can learn more about any package changes and choose the one you want. Click Update system . Confirm the update completed successfully in the dashboard. Verification From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Systems . If the update was successful, the system status is Up to date . If the system status is Error or Unresponsive , the system did not update properly. Click the Status to learn more about the failure. If the system status is Error , you can try the update again. Click the Error status, then click Retry . Additional resources How to start the upgrade process of an Edge Management deployed system .

Commands:
Chapter 9. Installing a three-node cluster on vSphere In OpenShift Container Platform version 4.13, you can install a three-node cluster on VMware vSphere. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. 9.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: compute: - name: worker platform: {} replicas: 0 If you are deploying a cluster with user-provisioned infrastructure: Configure your application ingress load balancer to route HTTP and HTTPS traffic to the control plane nodes. In a three-node cluster, the Ingress Controller pods run on the control plane nodes. For more information, see the "Load balancing requirements for user-provisioned infrastructure". After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on vSphere with user-provisioned infrastructure". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 9.2. steps Installing a cluster on vSphere with customizations Installing a cluster on vSphere with user-provisioned infrastructure

Commands:
compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
Chapter 7. Choosing and obtaining a Red Hat Ansible Automation Platform installer Choose the Red Hat Ansible Automation Platform installer you need based on your Red Hat Enterprise Linux environment internet connectivity. Review the following scenarios to decide which Red Hat Ansible Automation Platform installer meets your needs. 7.1. Installing with internet access Choose the Red Hat Ansible Automation Platform installer if your Red Hat Enterprise Linux environment is connected to the internet. Installing with internet access retrieves the latest required repositories, packages, and dependencies. Choose one of the following ways to set up your Ansible Automation Platform installer. Tarball install Navigate to the Red Hat Ansible Automation Platform download page. Click Download Now for the Ansible Automation Platform <latest-version> Setup . Extract the files: USD tar xvzf ansible-automation-platform-setup-<latest-version>.tar.gz RPM install Install Ansible Automation Platform Installer Package v.2.4 for RHEL 8 for x86_64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms ansible-automation-platform-installer v.2.4 for RHEL 9 for x86-64 USD sudo dnf install --enablerepo=ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms ansible-automation-platform-installer Note dnf install enables the repo as the repo is disabled by default. When you use the RPM installer, the files are placed under the /opt/ansible-automation-platform/installer directory. 7.2. Installing without internet access Use the Red Hat Ansible Automation Platform Bundle installer if you are unable to access the internet, or would prefer not to install separate components and dependencies from online repositories. Access to Red Hat Enterprise Linux repositories is still needed. All other dependencies are included in the tar archive. Procedure Go to the Red Hat Ansible Automation Platform download page. Click Download Now for the Ansible Automation Platform <latest-version> Setup Bundle . Extract the files: USD tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz

Commands:
tar xvzf ansible-automation-platform-setup-<latest-version>.tar.gz
sudo dnf install --enablerepo=ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms ansible-automation-platform-installer
sudo dnf install --enablerepo=ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms ansible-automation-platform-installer
tar xvzf ansible-automation-platform-setup-bundle-<latest-version>.tar.gz
Chapter 3. Authentication and Interoperability SSSD now enables the administrator to select which domains from the AD forest can be contacted In some environments, only a subset of domains in a joined Active Directory (AD) forest can be reached. Attempting to contact an unreachable domain might cause unwanted timeouts or switch the System Security Services Daemon (SSSD) to offline mode. To prevent this, the administrator can now configure a list of domains to which SSSD connects by setting the ad_enabled_domains option in the /etc/sssd/sssd.conf/ file. For details, see the sssd-ad(5) man page. (BZ#1324428) SSSD now enables selecting a list of PAM services that will not receive any environmental variables from pam_sss In some cases, it is not desirable to propagate environment variables set by the pam_sss Pluggable Authentication Module (PAM). For example, when using the sudo -i command, users might want to transfer the KRB5CCNAME variable of the original user to the target environment. Previously, when a non-privileged user executed the sudo -i command to become another non-privileged user, the new non-privileged user did not have the permissions to read the Kerberos credentials cache that KRB5CCNAME pointed to. For this use case, this update adds a new option named pam_response_filter . Using pam_response_filter , the administrator can list PAM services (such as sudo-i ) that do not receive any environmental variables (such as KRB5CCNAME ) during login. Now, if pam_response_filter lists sudo-i , a user can switch from one non-privileged user to another without KRB5CCNAME being set in the target environment. (BZ#1329378) IdM servers can now be configured to require TLS 1.2 or better Version 1.2 of the Transport Layer Security (TLS) protocol is considered significantly more secure than versions. This update enables you to configure your Identity Management (IdM) server to forbid communication using protocols that are less secure than TLS 1.2. For details, see the following Red Hat Knowledgebase article: https://access.redhat.com/articles/2801181 . (BZ# 1367026 ) pam_faillock can be now configured with unlock_time=never The pam_faillock module now allows specifying using the unlock_time=never option that the user authentication lock caused by multiple authentication failures should never expire. (BZ#1404832) The libkadm5* libraries have been moved to the libkadm5 package In Red Hat Enterprise Linux 6.9, the libkadm5* libraries have been moved from the krb5-libs to the new libkadm5 package. As a consequence, yum is not able to downgrade the krb5-libs package automatically. Before downgrading, remove the libkadm5 package manually: After you have manually removed the package, use the yum downgrade command to downgrade the krb5-libs package to a version. (BZ#1351284)

Commands:
rpm -e --nodeps libkadm5
Chapter 1. Use Case Considerations Because Amazon Web Services is an image-only service, there are common Satellite use cases that do not work, or require extra configuration in an Amazon Web Service environment. If you plan to use Satellite on AWS, ensure that the use case scenarios that you want to use are available in an AWS environment. 1.1. Use Cases Known to Work You can perform the following Red Hat Satellite use cases on AWS: Managing Red Hat Subscriptions Importing Content Managing Errata Registering a Host Manually Red Hat Insights Realm Integration via IdM OpenSCAP Remote Execution Subscriptions Not all Red Hat subscriptions are eligible to run in public cloud environments. For more information about subscription eligibility, see the Red Hat Cloud Access Page . You can create additional organizations and then import additional manifests to the organizations. For more information, see Creating an Organization in the Content Management Guide . Multi-homed Satellite and Capsule Multi-homed Satellite is not supported. Multi-homed Capsule is supported, to implement this, you can configure Capsules with a load balancer. For more information, see Configuring Capsules with a Load Balancer . You must do this when Satellite Server or Capsule Server has different internal and external DNS host names and there is no site-to-site VPN connection between the locations where you deploy Satellite Server and Capsule Server. On demand content sources You can use the On demand download policy to reduce the storage footprint of the server that runs Satellite. When you set the download policy to On Demand , content syncs to Satellite Server or Capsule Server when a content host requests it. For more information, see Importing Content in the Content Management Guide . 1.2. Use Cases that Do Not Work In AWS, you cannot manage the DHCP. Because of this, most of Satellite Server's kickstart and PXE provisioning models are unusable. This includes: PXE Provisioning Discovery and Discovery Rules ISO Provisioning methods. PXE-Less Discovery (iPXE) Per-host ISO Generic ISO Full-host ISO

Commands:
Chapter 6. Microsoft Azure environment creation for hosting JBoss EAP Create the virtual machines that will host your JBoss EAP instances in your Microsoft Azure environment. The virtual machines must use an Azure size of Standard_A2 or higher. You can use either the Azure On-Demand premium images to create your virtual machines or create your own virtual machines manually. For Red Hat Enterprise Linux virtual machines, see the instructions on the Customer Portal: Using the On-Demand Marketplace Red Hat Enterprise Linux image in Azure . Manually creating and provisioning a Red Hat Enterprise Linux image for Azure . For Microsoft Windows Server virtual machines, see the Microsoft Azure documentation for instructions on creating a Windows Server virtual machine in Microsoft Azure. Note JBoss EAP Azure virtual machine images is now available in the marketplace. Important If you are configuring JBoss EAP high availability, you must create your virtual machines inside the same virtual network.

Commands: