mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 14. Creating and Maintaining Snapshots with Snapper A snapshot volume is a point in time copy of a target volume that provides a way to revert a file system back to an earlier state. Snapper is a command-line tool to create and maintain snapshots for Btrfs and thinly-provisioned LVM file systems. 14.1. Creating Initial Snapper Configuration Snapper requires discrete configuration files for each volume it operates on. You must set up the configuration files manually. By default, only the root user is allowed to perform snapper commands. Warning If you are using thin provisioning, monitor free space in the thin-pool. A fully consumed thin pool can result in data loss. For more information, see Thinly-Provisioned Logical Volumes (Thin Volumes) in the Red Hat Enterprise Linux 7 Logical Volume Manager Administration Guide . Note that the Btrfs tools and file system are provided as a Technology Preview, which make them unsuitable for production systems. Although it is possible to allow a user or group other than root to use certain Snapper commands, Red Hat recommends that you do not add elevated permissions to otherwise unprivileged users or groups. Such a configuration bypasses SELinux and could pose a security risk. Red Hat recommends that you review these capabilities with your Security Team and consider using the sudo infrastructure instead. Note Btrfs is available as a Technology Preview feature in Red Hat Enterprise Linux 7 but has been deprecated since the Red Hat Enterprise Linux 7.4 release. It will be removed in a future major release of Red Hat Enterprise Linux. For more information, see Deprecated Functionality in the Red Hat Enterprise Linux 7.4 Release Notes. Procedure 14.1. Creating a Snapper Configuration File Create or choose either: A thinly-provisioned logical volume with a Red Hat supported file system on top of it, or A Btrfs subvolume. Mount the file system. Create the configuration file that defines this volume. For LVM2: For example, to create a configuration file called lvm_config on an LVM2 subvolume with an ext4 file system, mounted at /lvm_mount, use: For Btrfs: The -c config_name option specifies the name of the configuration file. The create-config tells snapper to create a configuration file. The -f file_system tells snapper what file system to use; if this is omitted snapper will attempt to detect the file system. The /mount-point is where the subvolume or thinly-provisioned LVM2 file system is mounted. Alternatively, to create a configuration file called btrfs_config , on a Btrfs subvolume that is mounted at /btrfs_mount , use: The configuration files are stored in the /etc/snapper/configs/ directory.

Commands:
snapper -c config_name create-config -f "lvm( fs_type )" /mount-point
snapper -c lvm_config create-config -f "lvm(ext4)" /lvm_mount
snapper -c config_name create-config -f btrfs /mount-point
snapper -c btrfs_config create-config -f btrfs /btrfs_mount
Chapter 5. Revoking privileges and access to an OpenShift Dedicated cluster As cluster owner, you can revoke admin privileges and user access to a OpenShift Dedicated cluster. 5.1. Revoking administrator privileges from a user Follow the steps in this section to revoke dedicated-admin privileges from a user. Prerequisites You logged in to OpenShift Cluster Manager . You created an OpenShift Dedicated cluster. You have configured a GitHub identity provider for your cluster and added an identity provider user. You granted dedicated-admin privileges to a user. Procedure Navigate to OpenShift Cluster Manager and select your cluster. Click the Access control tab. In the Cluster Roles and Access tab, select to a user and click Delete . Verification After revoking the privileges, the user is no longer listed as part of the dedicated-admins group under Access control Cluster Roles and Access on the OpenShift Cluster Manager page for your cluster. 5.2. Revoking user access to a cluster You can revoke cluster access from an identity provider user by removing them from your configured identity provider. You can configure different types of identity providers for your OpenShift Dedicated cluster. The following example procedure revokes cluster access for a member of a GitHub organization or team that is configured for identity provision to the cluster. Prerequisites You have an OpenShift Dedicated cluster. You have a GitHub user account. You have configured a GitHub identity provider for your cluster and added an identity provider user. Procedure Navigate to github.com and log in to your GitHub account. Remove the user from your GitHub organization or team: If your identity provider configuration uses a GitHub organization, follow the steps in Removing a member from your organization in the GitHub documentation. If your identity provider configuration uses a team within a GitHub organization, follow the steps in Removing organization members from a team in the GitHub documentation. Verification After removing the user from your identity provider, the user cannot authenticate into the cluster.

Commands:
7.3. RHEA-2013:1728 - new packages: openhpi32 New openhpi32 packages are now available for Red Hat Enterprise Linux 6. OpenHPI provides an open source implementation of the Service Availability Forum (SAF) Hardware Platform Interface (HPI). HPI is an abstracted interface for managing computer hardware, typically chassis- and rack-based servers. HPI includes resource modeling; access to and control over sensor, control, watchdog, and inventory data associated with resources; abstracted System Event Log interfaces; hardware events and alarms; and a managed hot swap interface. This is version 3.2 of the OpenHPI project. This enhancement update adds the openhpi32 packages to Red Hat Enterprise Linux 6. (BZ# 927897 ) All users who require openhpi32 are advised to install these new packages.

Commands:
function::thread_indent Name function::thread_indent - returns an amount of space with the current task information Synopsis Arguments delta the amount of space added/removed for each call Description This function returns a string with appropriate indentation for a thread. Call it with a small positive or matching negative delta. If this is the real outermost, initial level of indentation, then the function resets the relative timestamp base to zero. The timestamp is as per provided by the __indent_timestamp function, which by default measures microseconds.

Commands:
thread_indent:string(delta:long)
4. We Need Feedback! If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise Linux 6 and the component doc-DM_Multipath . When submitting a bug report, be sure to mention the manual's identifier: If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, include the section number and some of the surrounding text so we can find it easily.

Commands:
rh-DM_Multipath(EN)-6 (2017-3-8T15:15)
3.3. OpenSSL Intel AES-NI Engine The Intel Advanced Encryption Standard (AES) New Instructions (AES-NI) engine is available for certain Intel processors, and allows for extremely fast hardware encryption and decryption. Note For a list of Intel processors that support the AES-NI engine, see: Intel's ARK . The AES-NI engine is automatically enabled if the detected processor is among the supported ones. To check that the processor is supported, follow the steps below: Ensure that the processor has the AES instruction set: As root, run the following commands and compare their outputs. Significantly better performance of the latter command indicates that AES-NI is enabled. Note that the outputs below are shortened for brevity: To test the speed of OpenSSH you can run a command like the following: See Intel(R) Advanced Encryption Standard Instructions (AES-NI) for details about the AES-NI engine.

Commands:
~]# grep -m1 -o aes /proc/cpuinfo aes
~]# openssl speed aes-128-cbc The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 99696.17k 107792.98k 109961.22k 110559.91k 110742.19k
~]# openssl speed -evp aes-128-cbc The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128-cbc 800450.23k 873269.82k 896864.85k 903446.19k 902752.94k
~]# dd if=/dev/zero count=100 bs=1M | ssh -c aes128-cbc localhost "cat >/dev/null" root@localhost's password: 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 4.81868 s, 21.8 MB/s
Chapter 90. Plugin schema reference Used in: Build Property Property type Description name string The unique name of the connector plugin. Will be used to generate the path where the connector artifacts will be stored. The name has to be unique within the KafkaConnect resource. The name has to follow the following pattern: ^[a-z][-_a-z0-9]*[a-z]USD . Required. artifacts JarArtifact , TgzArtifact , ZipArtifact , MavenArtifact , OtherArtifact array List of artifacts which belong to this connector plugin. Required.

Commands:
8.7. Configuring a VNC Server To configure a VNC server, use the Remote Desktop application in System > Preferences . Alternatively, you can run the vino-preferences command. Use the following step set up a dedicated VNC server session: If needed, Create and then Edit the ~/.vnc/xstartup file to start a GNOME session whenever vncserver is started. The first time you run the vncserver script it will ask you for a password you want to use for your VNC session. For more information on vnc server files refer to the Red Hat Enterprise Linux Installation Guide .

Commands:
7.156. nfs-utils-lib 7.156.1. RHBA-2013:0467 - nfs-utils-lib bug fix update Updated nfs-utils-lib packages that fix one bug are now available for Red Hat Enterprise Linux 6. The nfs-utils-lib packages provide support libraries that programs in the nfs-utils package require. Bug Fix BZ# 804812 When building the list of local realms, idmapd overwrote the string buffer, which is used to keep that list, every time a new realm was added to the list. As a consequence, the idmapd daemon logged only the last local realm added to the list. This update modifies the source code so the realms are correctly appended to the string buffer and idmapd now logs the complete list of the local realms as expected. Also, buffer size calculation has been corrected. Users of nfs-utils-lib are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 7 is available on the following architectures: [1] 64-bit AMD 64-bit Intel IBM POWER7+ (big endian) IBM POWER8 (big endian) [2] IBM POWER8 (little endian) [3] IBM POWER9 (little endian) [4] [5] 64-bit IBM Z [4] [6] 64-bit ARM [4] The Red Hat Enterprise Linux 7.9 is distributed with the kernel version 3.10.0-1160, which provides support for the following architectures: 64-bit AMD 64-bit Intel IBM POWER7+ (big endian) IBM POWER8 (big endian) IBM POWER8 (little endian) 64-bit IBM Z (kernel version 3.10) Note The IBM POWER9 (little endian) and 64-bit IBM Z - Structure A architectures was retired on May 31, 2021. The 64-bit ARM architecture was retired on August 6, 2020, as per the RHEL Life Cycle . [1] Note that the Red Hat Enterprise Linux 7 installation is supported only on 64-bit hardware. Red Hat Enterprise Linux 7 is able to run 32-bit operating systems, including versions of Red Hat Enterprise Linux, as virtual machines. [2] Red Hat Enterprise Linux 7 POWER8 (big endian) are currently supported as KVM guests on Red Hat Enterprise Linux 7 POWER8 systems that run the KVM hypervisor, and on PowerVM. [3] Red Hat Enterprise Linux 7 POWER8 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 POWER8 systems that run the KVM hypervisor, and on PowerVM. In addition, Red Hat Enterprise Linux 7 POWER8 (little endian) guests are supported on Red Hat Enterprise Linux 7 POWER9 systems that run the KVM hypervisor in POWER8-compatibility mode on version 4.14 kernel using the kernel-alt package. [4] This architecture is supported with the kernel version 4.14, provided by the kernel-alt packages. For details, see the Red Hat Enterprise Linux 7.5 Release Notes . [5] Red Hat Enterprise Linux 7 POWER9 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 POWER9 systems that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package, and on PowerVM. [6] Red Hat Enterprise Linux 7 for IBM Z (both the 3.10 kernel version and the 4.14 kernel version) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 for IBM Z hosts that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package.

Commands:
Chapter 8. Troubleshooting and deleting remaining resources during Uninstall Occasionally some of the custom resources managed by an operator may remain in "Terminating" status waiting on the finalizer to complete, although you have performed all the required cleanup tasks. In such an event you need to force the removal of such resources. If you do not do so, the resources remain in the "Terminating" state even after you have performed all the uninstall steps. Check if the openshift-storage namespace is stuck in Terminating state upon deletion. Output: Check for the NamespaceFinalizersRemaining and NamespaceContentRemaining messages in the STATUS section of the command output and perform the step for each of the listed resources. Example output : Delete all the remaining resources listed in the step. For each of the resources to be deleted, do the following: Get the object kind of the resource which needs to be removed. See the message in the above output. Example : message: Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io Here cephobjectstoreuser.ceph.rook.io is the object kind. Get the Object name corresponding to the object kind. Example : Example output: Patch the resources. Example: Output: Verify that the openshift-storage project is deleted. Output: If the issue persists, reach out to Red Hat Support .

Commands:
oc get project -n <namespace>
NAME DISPLAY NAME STATUS openshift-storage Terminating
oc get project openshift-storage -o yaml
status: conditions: - lastTransitionTime: "2020-07-26T12:32:56Z" message: All resources successfully discovered reason: ResourcesDiscovered status: "False" type: NamespaceDeletionDiscoveryFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All legacy kube types successfully parsed reason: ParsedGroupVersions status: "False" type: NamespaceDeletionGroupVersionParsingFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All content successfully deleted, may be waiting on finalization reason: ContentDeleted status: "False" type: NamespaceDeletionContentFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some resources are remaining: cephobjectstoreusers.ceph.rook.io has 1 resource instances' reason: SomeResourcesRemain status: "True" type: NamespaceContentRemaining - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io in 1 resource instances' reason: SomeFinalizersRemain status: "True" type: NamespaceFinalizersRemaining
oc get <Object-kind> -n <project-name>
oc get cephobjectstoreusers.ceph.rook.io -n openshift-storage
NAME AGE noobaa-ceph-objectstore-user 26h
oc patch -n <project-name> <object-kind>/<object-name> --type=merge -p '{"metadata": {"finalizers":null}}'
oc patch -n openshift-storage cephobjectstoreusers.ceph.rook.io/noobaa-ceph-objectstore-user --type=merge -p '{"metadata": {"finalizers":null}}'
cephobjectstoreuser.ceph.rook.io/noobaa-ceph-objectstore-user patched
oc get project openshift-storage
Error from server (NotFound): namespaces "openshift-storage" not found
25.2. Locating Log Files A list of log files maintained by rsyslogd can be found in the /etc/rsyslog.conf configuration file. Most log files are located in the /var/log/ directory. Some applications such as httpd and samba have a directory within /var/log/ for their log files. You may notice multiple files in the /var/log/ directory with numbers after them (for example, cron-20100906 ). These numbers represent a time stamp that has been added to a rotated log file. Log files are rotated so their file sizes do not become too large. The logrotate package contains a cron task that automatically rotates log files according to the /etc/logrotate.conf configuration file and the configuration files in the /etc/logrotate.d/ directory.

Commands:
4.294. sg3_utils 4.294.1. RHBA-2011:1231 - sg3_utils bug fix update Updated sg3_utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sg3_utils packages contain a collection of tools for SCSI devices that use the Linux SCSI generic (sg) interface. It includes utilities for database copying based on "dd" syntax and semantics (the "sg_dd", "sgp_dd" and "sgm_dd" commands), INQUIRY data checking and associated pages ("sg_inq"), mode and log page checking ("sg_modes" and "sg_logs"), disk spinning ("sg_start") and self-tests ("sg_senddiag"), as well as other utilities. It also contains the rescan-scsi-bus.sh script. Bug Fix BZ# 628553 When scanning for iSCSI devices, if no device existed with a Logical Unit Number (LUN) of "0", then the rescan-scsi-bus.sh shell script failed to detect any other devices as well. With this update, the rescan-scsi-bus.sh script detects all iSCSI devices even if there is no device with LUN of "0". All users of sg3_utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Ansible based deployment workflow You can use Ansible to deploy Red Hat Hyperconverged Infrastructure for Virtualization on a single node or on 3 to 12 nodes. The preparation of the inventory file based on the user requirements is a one time process and is created with the help of the example inventory files available. The workflow for deploying RHHI for Virtualization using Ansible is as follows: Check requirements. Verify that your planned deployment meets support requirements: Requirements , and fill in the installation checklist so that you can refer to it during the deployment process. Install operating systems. Install an operating system on each physical machine that will act as a hyperconverged host: Installing hyperconverged hosts . (Optional) Install an operating system on each physical or virtual machine that will act as an Network-Bound Disk Encryption (NBDE) key server: Installing NBDE key servers . Modify firewall rules for additional software. (Optional) Modify firewall rules for disk encryption: Section 5.1, "Modifying firewall rules for disk encryption" . Configure authentication between hyperconverged hosts. Configure key-based SSH authentication without a password to enable automated configuration of the hosts: Configure key-based SSH authentication . (Optional) Configure disk encryption. Configure NBDE key servers . Configure hyperconverged hosts as NBDE clients . Define the details of your environment in inventory and playbook files: Defining deployment details Execute the Ansible playbook to deploy RHHI for Virtualization: Executing the deployment playbook Verify your deployment .

Commands:
probe::scsi.ioentry Name probe::scsi.ioentry - Prepares a SCSI mid-layer request Synopsis Values disk_major The major number of the disk (-1 if no information) device_state_str The current state of the device, as a string device_state The current state of the device req_addr The current struct request pointer, as a number disk_minor The minor number of the disk (-1 if no information)

Commands:
scsi.ioentry
Chapter 3. Red Hat build of Keycloak Realm Import 3.1. Importing a Red Hat build of Keycloak Realm Using the Red Hat build of Keycloak Operator, you can perform a realm import for the Keycloak Deployment. Note If a Realm with the same name already exists in Red Hat build of Keycloak, it will not be overwritten. The Realm Import CR only supports creation of new realms and does not update or delete those. Changes to the realm performed directly on Red Hat build of Keycloak are not synced back in the CR. 3.1.1. Creating a Realm Import Custom Resource The following is an example of a Realm Import Custom Resource (CR): apiVersion: k8s.keycloak.org/v2alpha1 kind: KeycloakRealmImport metadata: name: my-realm-kc spec: keycloakCRName: <name of the keycloak CR> realm: ... This CR should be created in the same namespace as the Keycloak Deployment CR, defined in the field keycloakCRName . The realm field accepts a full RealmRepresentation . The recommended way to obtain a RealmRepresentation is by leveraging the export functionality Importing and Exporting Realms . Export the Realm to a single file. Convert the JSON file to YAML. Copy and paste the obtained YAML file as body for the realm key, making sure the indentation is correct. 3.1.2. Applying the Realm Import CR Use oc to create the CR in the correct cluster namespace: Create YAML file example-realm-import.yaml : apiVersion: k8s.keycloak.org/v2alpha1 kind: KeycloakRealmImport metadata: name: my-realm-kc spec: keycloakCRName: <name of the keycloak CR> realm: id: example-realm realm: example-realm displayName: ExampleRealm enabled: true Apply the changes: oc apply -f example-realm-import.yaml To check the status of the running import, enter the following command: oc get keycloakrealmimports/my-realm-kc -o go-template='{{range .status.conditions}}CONDITION: {{.type}}{{"\n"}} STATUS: {{.status}}{{"\n"}} MESSAGE: {{.message}}{{"\n"}}{{end}}' When the import has successfully completed, the output will look like the following example: CONDITION: Done STATUS: true MESSAGE: CONDITION: Started STATUS: false MESSAGE: CONDITION: HasErrors STATUS: false MESSAGE:

Commands:
apiVersion: k8s.keycloak.org/v2alpha1 kind: KeycloakRealmImport metadata: name: my-realm-kc spec: keycloakCRName: <name of the keycloak CR> realm:
apiVersion: k8s.keycloak.org/v2alpha1 kind: KeycloakRealmImport metadata: name: my-realm-kc spec: keycloakCRName: <name of the keycloak CR> realm: id: example-realm realm: example-realm displayName: ExampleRealm enabled: true
apply -f example-realm-import.yaml
get keycloakrealmimports/my-realm-kc -o go-template='{{range .status.conditions}}CONDITION: {{.type}}{{"\n"}} STATUS: {{.status}}{{"\n"}} MESSAGE: {{.message}}{{"\n"}}{{end}}'
CONDITION: Done STATUS: true MESSAGE: CONDITION: Started STATUS: false MESSAGE: CONDITION: HasErrors STATUS: false MESSAGE:
Appendix A. Using your Red Hat subscription Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Managing your subscriptions Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. In the menu bar, click Subscriptions to view and manage your subscriptions. Revised on 2025-03-12 11:42:35 UTC

Commands: