mtpti5iD/redhat-docs_dataset huggingface dataset:
4.8. Configuring Satellite errata viewing for a virtual machine In the Administration Portal, you can configure a virtual machine to display the available errata. The virtual machine needs to be associated with a Red Hat Satellite server to show available errata. Red Hat Virtualization 4.4 supports viewing errata with Red Hat Satellite 6.6. Prerequisites The Satellite server must be added as an external provider. The Manager and any virtual machines on which you want to view errata must all be registered in the Satellite server by their respective FQDNs. This ensures that external content host IDs do not need to be maintained in Red Hat Virtualization. Important Virtual machines added using an IP address cannot report errata. The host that the virtual machine runs on also needs to be configured to receive errata information from Satellite. The virtual machine must have the ovirt-guest-agent package installed. This package enables the virtual machine to report its host name to the Red Hat Virtualization Manager, which enables the Red Hat Satellite server to identify the virtual machine as a content host and report the applicable errata. The virtual machine must be registered to the Red Hat Satellite server as a content host. Use Red Hat Satellite remote execution to manage packages on hosts. Note The Katello agent is deprecated and will be removed in a future Satellite version. Migrate your processes to use the remote execution feature to update clients remotely. Procedure Click Compute Virtual Machines and select a virtual machine. Click Edit . Click the Foreman/Satellite tab. Select the required Satellite server from the Provider drop-down list. Click OK . Additional resources Setting up Satellite errata viewing for a host in the Administration Guide Installing the Guest Agents, Tools, and Drivers on Linux in the Virtual Machine Management Guide for Red Hat Enterprise Linux virtual machines. Installing the Guest Agents, Tools, and Drivers on Windows in the Virtual Machine Management Guide for Windows virtual machines.

Commands:
5.4.12. Removing Logical Volumes To remove an inactive logical volume, use the lvremove command. If the logical volume is currently mounted, unmount the volume before removing it. In addition, in a clustered environment you must deactivate a logical volume before it can be removed. The following command removes the logical volume /dev/testvg/testlv from the volume group testvg . Note that in this case the logical volume has not been deactivated. You could explicitly deactivate the logical volume before removing it with the lvchange -an command, in which case you would not see the prompt verifying whether you want to remove an active logical volume.

Commands:
lvremove /dev/testvg/testlv Do you really want to remove active logical volume "testlv"? [y/n]: y Logical volume "testlv" successfully removed
18.2.4. Installation Phase 3 In installation phase 3 you will use anaconda in graphical, text-based, or cmdline mode: Graphical mode This can be used through a VNC client (recommended) or through an X11 server. You can use your mouse and keyboard to navigate through the screens, click buttons, and enter text in fields. Text-based mode This interface does not offer all interface elements of the GUI and does not support all settings. Use this for interactive installations if you cannot use a VNC client or X11 server. cmdline mode This is intended for automated installations on System z. (Refer to Section 26.6, "Parameters for Kickstart Installations" ) If you have a slow network connection or prefer a text-based installation, do not use X11 forwarding when logging in over the network and do not set the display= variable in the parameter file (refer to Section 26.4, "VNC and X11 Parameters" for details). In Red Hat Enterprise Linux 6.9 the text-based installation has been reduced to minimize user interaction. Features like installation on FCP-attached SCSI devices, changing partition layout, or package selection are only available with the graphical user interface installation. Use the graphical installation whenever possible. (Refer to Chapter 23, Installation Phase 3: Installing Using Anaconda .)

Commands:
Chapter 5. Installing a three-node cluster on Nutanix In OpenShift Container Platform version 4.18, you can install a three-node cluster on Nutanix. 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. 5.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: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... 5.2. steps Installing a cluster on Nutanix

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
7.254. tigervnc 7.254.1. RHBA-2013:0478 - tigervnc bug fix and enhancement update Updated tigervnc packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Virtual Network Computing (VNC) is a remote display system which allows you to view a computing 'desktop' environment not only on the machine where it is running, but from anywhere on the Internet and from a wide variety of machine architectures. This package contains a client which will allow you to connect to other desktops running a VNC server. Bug Fixes BZ#688624 When the Xvnc server was started by the vncserver init script, but no password file existed, the initscript failed without displaying a message. This bug is now fixed and the "VNC password for user is not configured" message appears when the password is not configured for the Xvnc session. BZ#843714 Previously, the user was not allowed to change the value of the AcceptPointerEvents parameter while Xvnc was running. As a consequence, when the "vncconfig -set AcceptPointerEvents=1" command was used to enable and "vncconfig -set AcceptPointerEvents=0", to disable mouse input for VNC session, it failed with an error message, similar to the following: Setting param AcceptPointerEvents=0 failed Now the user is allowed to change the value of the AcceptPointerEvents parameter and the mouse input for a VNC session can be enabled or disabled while Xvnc is running. Enhancement BZ#844486 The tigervnc packages have been updated to match the latest X server version. Users of tigervnc are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 10. Querying domain information using SSSD Security System Services Daemon (SSSD) can list domains in Identity Management (IdM) as well as the domains in Active Directory that is connected to IdM by a cross-forest trust. 10.1. Listing domains using sssctl You can use the sssctl domain-list command to debug problems with the domain topology. Note The status might not be available immediately. If the domain is not visible, repeat the command. Prerequisites You must be logged in with administrator privileges The sssctl tool is available on RHEL 7 and RHEL 8 systems. Procedure To display help for the sssctl command, enter: To display a list of available domains, enter: The list includes domains in the cross-forest trust between Active Directory and Identity Management. 10.2. Verifying the domain status using sssctl You can use the sssctl domain-status command to debug problems with the domain topology. Note The status might not be available immediately. If the domain is not visible, repeat the command. Prerequisites You must be logged in with administrator privileges The sssctl tool is available on RHEL 7 and RHEL 8 systems. Procedure To display help for the sssctl command, enter: To display user data for a particular domain, enter: The domain idm.example.com is online and visible from the client where you applied the command. If the domain is not available, the result is:

Commands:
sssctl --help .
sssctl domain-list implicit_files idm.example.com ad.example.com sub1.ad.example.com
sssctl --help
sssctl domain-status idm.example.com Online status: Online Active servers: IPA: server.idm.example.com Discovered IPA servers: - server.idm.example.com
sssctl domain-status ad.example.com Unable to get online status
Chapter 25. Creating a new IT_Orders case project Create a new IT_Orders project in Business Central to gain an understanding of all of the required assets and how they are used in the project. Procedure Log in to Business Central and go to Menu Design Projects . Business Central provides a default space called MySpace . You can use the default space to create and test example projects. Click the Add Project drop-down arrow and select the Case project option: In the Add Project window, enter IT_Orders_New in the Name field and enter a project Description . Click Add to add the project. The Assets view of the project opens.

Commands:
Chapter 1. Getting started overview Use Red Hat AMQ Streams to create and set up Kafka clusters, then connect your applications and services to those clusters. This guide describes how to install and start using AMQ Streams on OpenShift Container Platform. You can install the AMQ Streams operator from the OperatorHub in the OpenShift web console. The AMQ Streams operator understands how to install and manage Kafka components. Installing from the OperatorHub provides a standard configuration of AMQ Streams that allows you to take advantage of automatic updates. When the AMQ Streams operator is installed, it provides the resources to install instances of Kafka components. After installing a Kafka cluster, you can start producing and consuming messages. Note If you require more flexibility with your deployment, you can use the installation artifacts provided with AMQ Streams. For more information on using the installation artifacts, see Deploying and Upgrading AMQ Streams on OpenShift . 1.1. Using the OperatorHub The OperatorHub is the web console interface of the OpenShift Container Platform for installing operators. Using the OperatorHub, you can install the AMQ Streams operator directly from the OpenShift web console. You can choose to install the AMQ Streams operator in one of the following ways: AMQ Streams operator only Install the AMQ Streams operator directly . Red Hat Integration operator (deprecated) If you have more than one Red Hat Integration subscription, you can use the Red Hat Integration operator to install and update the AMQ Streams operator, as well as the operators for all subscribed Red Hat Integration components. For more information, see Installing the Red Hat Integration Operator . Note The Red Hat Integration operator has been deprecated and will be removed in the future. It will be available from the OperatorHub in OpenShift 4.6 to 4.10. 1.2. Prerequsites The following prerequisites are required for getting started with AMQ Streams. You have a Red Hat account. JDK 11 or later is installed. An OpenShift 4.6 to 4.10 cluster is available. The OpenShift oc command-line tool is installed and configured to connect to the running cluster. The steps to get started are based on using the OperatorHub in the OpenShift web console, but you'll also use the OpenShift oc CLI tool to perform certain operations. You'll need to connect to your OpenShift cluster using the oc tool. You can install the oc CLI tool from the web console by clicking the '?' help menu, then Command Line Tools . You can copy the required oc login details from the web console by clicking your profile name, then Copy login command . 1.3. Additional resources Strimzi Overview Deploying and Upgrading AMQ Streams on OpenShift Installing the Red Hat Integration Operator

Commands:
25.22. Configuring Maximum Time for Error Recovery with eh_deadline Important In most scenarios, you do not need to enable the eh_deadline parameter. Using the eh_deadline parameter can be useful in certain specific scenarios, for example if a link loss occurs between a Fibre Channel switch and a target port, and the Host Bus Adapter (HBA) does not receive Registered State Change Notifications (RSCNs). In such a case, I/O requests and error recovery commands all time out rather than encounter an error. Setting eh_deadline in this environment puts an upper limit on the recovery time, which enables the failed I/O to be retried on another available path by multipath. However, if RSCNs are enabled, the HBA does not register the link becoming unavailable, or both, the eh_deadline functionality provides no additional benefit, as the I/O and error recovery commands fail immediately, which allows multipath to retry. The SCSI host object eh_deadline parameter enables you to configure the maximum amount of time that the SCSI error handling mechanism attempts to perform error recovery before stopping and resetting the entire HBA. The value of the eh_deadline is specified in seconds. The default setting is off , which disables the time limit and allows all of the error recovery to take place. In addition to using sysfs , a default value can be set for all SCSI HBAs by using the scsi_mod.eh_deadline kernel parameter. Note that when eh_deadline expires, the HBA is reset, which affects all target paths on that HBA, not only the failing one. As a consequence, I/O errors can occur if some of the redundant paths are not available for other reasons. Enable eh_deadline only if you have a fully redundant multipath configuration on all targets.

Commands:
Chapter 1. Overview of Insights for Red Hat Enterprise Linux vulnerability service reporting The ability to convey the security exposure of your infrastructure to different stakeholders-DevOps team, security team, executive team-is vital. The vulnerability service enables you to download the following reports to analyze offline or share with others: Executive Reports. PDF summary and overview of the security vulnerability exposure your infrastructure, intended for executive audiences CVE reports. PDF report of selected, filtered CVEs to which your infrastructure is exposed, intended to highlight and share vulnerability data Vulnerability data export. Export of selected CVE data, based on filters you have in place when you perform the export, to a JSON or CSV file

Commands:
5.5.2.4. Access Control Access control is one area where file systems differ dramatically. Some file systems have no clear-cut access control model, while others are much more sophisticated. In general terms, most modern day file systems combine two components into a cohesive access control methodology: User identification Permitted action list User identification means that the file system (and the underlying operating system) must first be capable of uniquely identifying individual users. This makes it possible to have full accountability with respect to any operations on the file system level. Another often-helpful feature is that of user groups -- creating ad-hoc collections of users. Groups are most often used by organizations where users may be members of one or more projects. Another feature that some file systems support is the creation of generic identifiers that can be assigned to one or more users. , the file system must be capable of maintaining lists of actions that are permitted (or not permitted) against each file. The most commonly-tracked actions are: Reading the file Writing the file Executing the file Various file systems may extend the list to include other actions such as deleting, or even the ability to make changes related to a file's access control.

Commands:
22.4.3. Performing a Network Installation The installation program is network-aware and can use network settings for a number of functions. On System z, installation phases 2 and 3 take over the network configuration values specified previously either interactively or by means of a parameter or configuration file in installation phase 1. You can also instruct the installation program to consult additional software repositories later in the process. If you are installing via NFS, proceed to Section 22.4.4, "Installing via NFS" . If you are installing via Web or FTP, proceed to Section 22.4.5, "Installing via FTP, HTTP, or HTTPS" .

Commands:
20.4. Enabling and Changing a Quota Mode in a Data Center This procedure enables or changes the quota mode in a data center. You must select a quota mode before you can define quotas. You must be logged in to the Administration Portal to follow the steps of this procedure. Use Audit mode to test your quota to verify that it works as you expect it to. You do not need to have your quota in Audit mode to create or change a quota. Enabling and Changing Quota in a Data Center Click Compute Data Centers and select a data center. Click Edit . In the Quota Mode drop-down list, change the quota mode to Enforced . Click OK . If you set the quota mode to Audit during testing, then you must change it to Enforced in order for the quota settings to take effect.

Commands:
13.2. Enabling the Ctrl+Alt+Backspace Shortcut The Ctrl + Alt + Backspace shortcut key combination is used for terminating the X server. You might want to terminate the X server especially when: a program caused the X server to stop working. you need to switch from your logged-in session quickly. you have launched a program that failed. you cannot operate in the current session for various reason. your screen freezes. To enable the Ctrl + Alt + Backspace shortcut to forcibly terminate the X server by default for all users, you need to set the org.gnome.desktop.input-sources.xkb-options GSettings key. (For more information on GSettings keys, see Section 9.6, "GSettings Keys Properties" .) Procedure 13.2. Enabling the Ctrl-Alt-Backspace Shortcut Create a local database for machine-wide settings in /etc/dconf/db/local.d/00-input-sources : Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/input-sources : Update the system databases for the changes to take effect: Users must log out and back in again before the system-wide settings take effect. The Ctrl + Alt + Backspace key combination is now enabled. All users can terminate the X server quickly and easily and doing so bring themselves back to the login prompt.

Commands:
Enable Ctrl-Alt-Backspace for all users xkb-options=['terminate:ctrl_alt_bksp']
Lock the list of enabled XKB options /org/gnome/desktop/input-sources/xkb-options
dconf update
Chapter 11. Configuring project settings Starting with Red Hat Decision Manager 7.13, Business Central contains additional project setting categories in the new process designer. Prerequisites You have created a Business Central project. Procedure To access the project Settings tab, in Business Central go to Menu Design Projects . Click the project name. Click Settings to view or modify the following project settings: General Settings - Enables users to set the project's Name , Description , Group ID , Artifact ID , Version (GAV), and Development Mode attributes. It also includes the following options: URL - Use to specify a read-only URL for cloning a project as a git repository. Disable GAV conflict check - Determines whether to enable or disable the GAV conflict check. Disabling this feature enables projects to have the same GAV values. Allow child GAV edition - Allows GAV editions for sub-projects. Dependencies - Used to add dependencies either manually, by entering the Group ID , Artifact ID , and Version or from a repository project in Business Central. For each dependency, set select All or None for the Package white list option. KIE Bases - The new name for what was previously called Knowledge bases . You must specify a KIE base as the default. Provide the following details to add a Kie base: Name Included KIE bases Package Equal Behavior - Identity or Equality Event Processing Model - Stream or Cloud KIE sessions External Data Objects - Data objects are not explicitly defined within a project or project dependencies that a rule author may require. External data objects are usually provided by the Java runtime, for example, java.util.List . Validation - Maven repositories that are used to check the uniqueness of a project's GAV when creating a new project or module or when installing or deploying a project to a Maven repository. Service Tasks - The following service tasks can be added to a project: BusinessRuleTask - Execute a business rule task Decision Task - Execute a DMN decision task Email - Send email JMSSendTask - Send JMS Message Rest - Perform a Rest call ServiceTask - Execute a service task WebService - Perform a web service call Deployments - Deployments are divided in to the following categories: General Settings - Runtime Strategy , Persistence Unit Name , Persistence Mode , Audit Persistence Unit Name , and Audit Mode Marshalling strategies Global Event listeners Required roles Remoteable classes Task event listeners Configuration Environment entries Work item handlers Persistence - Persistence is divided in to the following categories: Persistence Unit Persistence Provider Data Source Properties - Used to set values for the following properties and also to create new properties: hibernate.dialect hibernate.max_fetch_depth hibernate.hbm2ddl.auto hibernate.show_sql hibernate.id.new_generator_mappings hibernate.transaction.jta.platform Project Persistable Data Objects Branch Management - Provides branch role access based on the branch name and assigned user roles. Click Save .

Commands:
Chapter 6. Checking greenboot scripts status To deploy applications or make other changes through the MicroShift API with tools other than kustomize manifests, you must wait until the greenboot health checks have finished. This ensures that your changes are not lost if greenboot rolls your rpm-ostree system back to an earlier state. The greenboot-healthcheck service runs one time and then exits. After greenboot has exited and the system is in a healthy state, you can proceed with configuration changes and deployments. 6.1. Checking the status of greenboot health checks Check the status of greenboot health checks before making changes to the system or during troubleshooting. You can use any of the following commands to help you ensure that greenboot scripts have finished running. Procedure To see a report of health check status, use the following command: USD systemctl show --property=SubState --value greenboot-healthcheck.service An output of start means that greenboot checks are still running. An output of exited means that checks have passed and greenboot has exited. Greenboot runs the scripts in the green.d directory when the system is a healthy state. An output of failed means that checks have not passed. Greenboot runs the scripts in red.d directory when the system is in this state and might restart the system. To see a report showing the numerical exit code of the service where 0 means success and non-zero values mean a failure occurred, use the following command: USD systemctl show --property=ExecMainStatus --value greenboot-healthcheck.service To see a report showing a message about boot status, such as Boot Status is GREEN - Health Check SUCCESS , use the following command: USD cat /run/motd.d/boot-status

Commands:
systemctl show --property=SubState --value greenboot-healthcheck.service
systemctl show --property=ExecMainStatus --value greenboot-healthcheck.service
cat /run/motd.d/boot-status