mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Summarizing cluster specifications 7.1. Summarizing cluster specifications by using a cluster version object You can obtain a summary of Red Hat OpenShift Service on AWS cluster specifications by querying the clusterversion resource. Prerequisites You have access to the cluster as a user with the dedicated-admin role. You have installed the OpenShift CLI ( oc ). Procedure Query cluster version, availability, uptime, and general status: USD oc get clusterversion Example output NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8 Obtain a detailed summary of cluster specifications, update availability, and update history: USD oc describe clusterversion Example output Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion # ... Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8 # ...

Commands:
oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8
oc describe clusterversion
Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8
4.146. libssh2 4.146.1. RHBA-2012:0431 - libssh2 bug fix update An updated libssh2 package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The libssh2 package provides a library that implements the SSH2 protocol. Bug Fixes BZ# 803389 Previously, an insufficient data type was used for certain bit shift operations in the libssh2 code. This could result in an arithmetic overflow, which caused the curl utility to terminate unexpectedly when downloading files larger than 2 GB over the SFTP protocol. With this update, the underlying code has been modified to use the correct data type and curl now works as expected in the scenario described. BZ# 805026 When sending a large amount of data over SSH, libssh2 could, under certain circumstances, fail to resume an interrupted key exchange. Instead of that, further data was erroneously sent, which caused the remote site to close the connection immediately. This update modifies the code of libssh2 so that libssh2 now properly resumes the interrupted key exchange before sending any further data. The connection remains open and the data transfer proceeds as expected. All users of libssh2 are advised to upgrade to this updated package, which fixes these bugs. After installing this updated package, all running applications using libssh2 have to be restarted for this update to take effect.

Commands:
Chapter 9. Troubleshooting DM Multipath If you have trouble implementing a multipath configuration, there are a variety of issues you can check for. The following issues may result in a slow or non-functioning multipath configuration: The multipath daemon is not running If you find you have trouble implementing a multipath configuration, ensure that the multipathd daemon is running, as described in Configuring DM Multipath . The multipathd daemon must be running to use multipathed devices. Issues with queue_if_no_path feature If a multipath device is configured with the features "1 queue_if_no_path" option, then any process that issues I/O hangs until one or more paths are restored. 9.1. Troubleshooting issues with queue_if_no_path feature If a multipath device is configured with the features "1 queue_if_no_path" option, then any process that issues I/O hangs until one or more paths are restored. To avoid this, set the no_path_retry N parameter in the /etc/multipath.conf file, where N is the number of times the system should retry a path. To use the features "1 queue_if_no_path" option without the described problem, you can disable the queueing policy at runtime for a particular LUN, for which all paths are unavailable. Procedure Disable queueing: For a specific device: For all devices: After you disable queueing, it will remain disabled until you restart or reload multipathd . Reset queueing to a value: For a specific device: For all devices: 9.2. Troubleshooting with the multipathd interactive console The multipathd -k command is an interactive interface to the multipathd daemon. Entering this command brings up an interactive multipath console. After executing this command, you can enter help to get a list of available commands and Ctrl + D to quit. Use the multipathd interactive console to troubleshoot problems you might have with your system. Procedure Display the multipath configuration, including the default values, before exiting the console: Ensure that multipath picked up all changes to the multipath.conf file: Ensure that the path checker is working properly: You can also run a single multipathd interactive command directly from the command line, without starting the interactive console. For example, to check that multipath picks up all changes to the multipath.conf file, run the following command:

Commands:
multipathd disablequeueing map device
multipathd disablequeueing maps
multipathd restorequeueing map device
multipathd restorequeueing maps
multipathd -k multipathd> show config multipathd> Ctrl + D
multipathd -k multipathd> reconfigure multipathd> Ctrl + D
multipathd -k multipathd> show paths multipathd> Ctrl + D
multipathd reconfigure
6.6.2. Related Books Red Hat Enterprise Linux Introduction to System Adminitration ; Red Hat, Inc - This companion manual provides an overview of concepts and techniques of system administration. The chapter titled Managing User Accounts and Resource Access has great information pertaining to user and group account management. System Administrators Guide ; Red Hat, Inc - This companion manual contains more information on managing users and groups as well as advanced permission configuration using ACLs. Refer to the chapters titled User and Group Configuration and Access Control Lists for details. Security Guide ; Red Hat, Inc - This companion manual provides security-related aspects of user accounts, namely choosing strong passwords.

Commands:
4.11. Configuring the time zone Red Hat Virtualization stores time zone configurations for virtual machines in /etc/ovirt-engine/conf/00-timezone.properties . This file contains default time zone values such as Etc/GMT=Greenwich Standard Time . It features mappings that are valid for Windows and non-Windows time zones. Important Do not edit the actual 00-timezone.properties file. Changes will be overwritten if you upgrade or restore the Manager. Do not change values that come directly from the operating system or the Manager. Procedure Create an override file in /etc/ovirt-engine/conf/ . The file name must begin with a value greater than 00 , so that the file appears after /etc/ovirt-engine/conf/00-timezone.properties , and ends with the extension, .properties . For example, 10-timezone.properties overrides the default file, 00-timezone.properties . The last file in the file list has precedence over earlier files. Add new time zones to that file. Be sure each key is a valid General time zone from the time zone database and the value is a valid Windows time zone: General Time zones used for non-Windows operating system types, must follow the standard time zone format for example, Etc/GMT or Asia/Jerusalem . Windows Time zones specifically supported on Windows for example, GMT Standard Time or Israel Standard Time . Restart the rhvm service: # systemctl restart ovirt-engine

Commands:
systemctl restart ovirt-engine
Chapter 6. Managing groups You can use Identity Service (keystone) groups to assign consistent permissions to multiple user accounts. 6.1. Configuring groups with the Dashboard You can use the dashboard to manage the membership of keystone groups. However, you must use the command-line to assign role permissions to a group. 6.1.1. Creating a group Log in to the dashboard as a user with administrative privileges. Select Identity > Groups . Click +Create Group . Enter a name and description for the group. Click Create Group . 6.1.2. Managing Group membership You can use the dashboard to manage the membership of keystone groups. Log in to the dashboard as a user with administrative privileges. Select Identity > Groups . Click Manage Members for the group that you want to edit. Use Add users to add a user to the group. If you want to remove a user, mark its checkbox and click Remove users .

Commands:
Chapter 5. Developer Previews Developer preview features included with Streams for Apache Kafka 2.7. As a Kafka cluster administrator, you can toggle a subset of features on and off using feature gates in the Cluster Operator deployment configuration. The feature gates available as developer previews are at an alpha level of maturity and disabled by default. Important Developer Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Developer Preview features in production environments. This Developer Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about the support scope, see Developer Preview Support Scope . 5.1. Tiered storage for Kafka brokers Streams for Apache Kafka now supports tiered storage for Kafka brokers as a developer preview, allowing you to introduce custom remote storage solutions as well as local storage. Due to its current limitations , it is not recommended for production environments. Remote storage configuration is specified using kafka.tieredStorage properties in the Kafka resource. You specify a custom remote storage manager to manage the tiered storage. Example custom tiered storage configuration kafka: tieredStorage: type: custom remoteStorageManager: className: com.example.kafka.tiered.storage.s3.S3RemoteStorageManager classPath: /opt/kafka/plugins/tiered-storage-s3/* config: # remote storage manager configuration 1 storage.bucket.name: my-bucket config: ... rlmm.config.remote.log.metadata.topic.replication.factor: 1 2 1 Configure the custom remote storage manager with the necessary settings. The keys are automatically prefixed with rsm.config and appended to the Kafka broker configuration. 2 Streams for Apache Kafka uses the TopicBasedRemoteLogMetadataManager for Remote Log Metadata Management (RLMM). Add RLMM configuration using an rlmm.config. prefix. Note If you want to use custom tiered storage, you must first add the tiered storage plugin to the Streams for Apache Kafka image by building a custom container image. See Tiered storage (early access) .

Commands:
kafka: tieredStorage: type: custom remoteStorageManager: className: com.example.kafka.tiered.storage.s3.S3RemoteStorageManager classPath: /opt/kafka/plugins/tiered-storage-s3/* config: # remote storage manager configuration 1 storage.bucket.name: my-bucket config: rlmm.config.remote.log.metadata.topic.replication.factor: 1 2
21.3.7. Adding a Samba (SMB) printer Follow this procedure to add a Samba printer: Note Note that in order to add a Samba printer, you need to have the samba-client package installed. You can do so by running, as root : For more information on installing packages with Yum, see Section 8.2.4, "Installing Packages" . Open the New Printer dialog (see Section 21.3.2, "Starting Printer Setup" ). In the list on the left, select Network Printer Windows Printer via SAMBA . Enter the SMB address in the smb:// field. Use the format computer name/printer share . In Figure 21.8, "Adding a SMB printer" , the computer name is dellbox and the printer share is r2 . Figure 21.8. Adding a SMB printer Click Browse to see the available workgroups/domains. To display only queues of a particular host, type in the host name (NetBios name) and click Browse . Select either of the options: Prompt user if authentication is required : user name and password are collected from the user when printing a document. Set authentication details now : provide authentication information now so it is not required later. In the Username field, enter the user name to access the printer. This user must exist on the SMB system, and the user must have permission to access the printer. The default user name is typically guest for Windows servers, or nobody for Samba servers. Enter the Password (if required) for the user specified in the Username field. Warning Samba printer user names and passwords are stored in the printer server as unencrypted files readable by root and the Linux Printing Daemon, lpd. Thus, other users that have root access to the printer server can view the user name and password you use to access the Samba printer. Therefore, when you choose a user name and password to access a Samba printer, it is advisable that you choose a password that is different from what you use to access your local Red Hat Enterprise Linux system. If there are files shared on the Samba print server, it is recommended that they also use a password different from what is used by the print queue. Click Verify to test the connection. Upon successful verification, a dialog box appears confirming printer share accessibility. Click Forward . Select the printer model. See Section 21.3.8, "Selecting the Printer Model and Finishing" for details.

Commands:
install samba-client
4.12. Mail 4.12.1. Sendmail In some releases of Red Hat Enterprise Linux 5, the sendmail Mail Transport Agent (MTA) accepted network connections from external hosts by default. In Red Hat Enterprise Linux 6, sendmail by default only accepts connections from the local system (localhost). To grant sendmail the ability to act as a server for remote hosts, perform one of the following steps: Edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also listen on network devices Comment out the DAEMON_OPTIONS line in /etc/mail/sendmail.mc . To put either of these changes into effect, install the sendmail-cf package, then regenerate /etc/mail/sendmail.cf . This is done by running the following commands:

Commands:
su -c 'yum install sendmail-cf' su -c 'make -C /etc/mail'
7.131. module-init-tools 7.131.1. RHBA-2015:1289 - module-init-tools bug fix update Updated module-init-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The module-init-tools packages include various programs needed for automatic loading and unloading of modules under 2.6 kernels, as well as other module management programs. Device drivers and file systems are two examples of loaded and unloaded modules. Bug Fix BZ# 1101045 On systems where the bridge module was not loaded, the "sysctl -p" command previously returned an error. This update moves several net.bridge.bridge-nf-call* parameters from the /etc/sysctl.conf file to the /etc/modprobe.d/dist.conf file, so that they take effect only when the bridge module is loaded, instead of being a part of the system startup. As a result, the described problem no longer occurs. Users of module-init-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Accessing your workbench IDE To access a workbench IDE, use the link provided in the OpenShift AI interface. Prerequisite You have created a data science project and a workbench. Procedure From the OpenShift AI dashboard, click Data Science Projects . Click the name of the project that contains the workbench. Click the Workbenches tab. If the status of the workbench is Running , skip to the step. If the status of the workbench is Stopped , in the Status column for the workbench, click Start . The Status column changes from Stopped to Starting when the workbench server is starting, and then to Running when the workbench has successfully started. Click the Open link to the workbench. Verification A new browser window opens for the workbench IDE.

Commands:
14.6. Create a VDB Source Model Procedure 14.3. Create a VDB Source Model Deploy your VDB. Launch the JDBC Import Wizard by clicking Import - Teiid Designer - JDBC Database >> Source Model . On the first page of the wizard select a valid connection profile for your deployed VDB. The wizard will detect that the connection profile is a Teiid VDB connection and a section will be displayed on the wizard page titled Teiid VDB Source Options . Note If Import as VDB source model is NOT checked, then the wizard will continue importing as a normal JDBC import On the Select Database Objects page, select a single schema to use in order to create as VDB source model. The final page shows the name of the resulting VDB source model. The name is NOT editable. Note The target Into Folder must NOT contain a model with the same name or the Finish button will be disabled. Note You can use your VDB source model like any other source model in your project. VDB source model tables can be used in your transformation queries and the view models will contain model imports to your VDB source models. However, when your view model is added to a VDB, any referenced VDB source models do NOT get added to your VDB. Instead, an import-vdb element reference is added in its place. If VDB imports exist for a VDB, the Show Import VDBs button will be enabled and allow viewing the names of the imported VDBs as shown below. Figure 14.1. VDB Editor

Commands:
Chapter 3. Debug Parameters These parameters allow you to set debug mode on a per-service basis. The Debug parameter acts as a global parameter for all services and the per-service parameters can override the effects of global parameter on individual services. Parameter Description BarbicanDebug Set to True to enable debugging OpenStack Key Manager (barbican) service. CinderDebug Set to True to enable debugging on OpenStack Block Storage (cinder) services. ConfigDebug Whether to run configuration management (e.g. Puppet) in debug mode. The default value is False . Debug Set to True to enable debugging on all services. The default value is False . GlanceDebug Set to True to enable debugging OpenStack Image Storage (glance) service. HeatDebug Set to True to enable debugging OpenStack Orchestration (heat) services. HorizonDebug Set to True to enable debugging OpenStack Dashboard (horizon) service. The default value is False . IronicDebug Set to True to enable debugging OpenStack Bare Metal (ironic) services. KeystoneDebug Set to True to enable debugging OpenStack Identity (keystone) service. ManilaDebug Set to True to enable debugging OpenStack Shared File Systems (manila) services. NeutronDebug Set to True to enable debugging OpenStack Networking (neutron) services. NovaDebug Set to True to enable debugging OpenStack Compute (nova) services. SaharaDebug Set to True to enable debugging OpenStack Clustering (sahara) services.

Commands:
8.19. bfa-firmware 8.19.1. RHBA-2014:1486 - bfa-firmware bug fix and enhancement update Updated bfa-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The bfa-firmware package contains the Brocade Fibre Channel Host Bus Adapter (HBA) Firmware to run Brocade Fibre Channel and CNA adapters. This package also supports the Brocade BNA network adapter. Note The bfa-firmware package has been upgraded to upstream version 3.2.23, which provides a number of bug fixes and enhancements over the version. (BZ# 1054467 ) All users of bfa-firmware are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
5.313. strace 5.313.1. RHBA-2012:1317 - strace bug fix and enhancement update Updated strace packages that fix a bug are now available for Red Hat Enterprise Linux 6. The strace packages provide an utility to intercept and record the system calls called and received by a running process. The strace utility can print a record of each system call, its arguments, and its return value. The strace utility is useful for diagnosing, debugging, and instructional purposes. Bug Fix BZ# 849052 Previously, the strace utility used magic breakpoints in the process startup code to detect and control process startup. Consequently, under certain circumstances, the %ebx register could be corrupted around the clone syscall within the libc_fork() function, which could cause an application to terminate unexpectedly with a segmentation fault while under strace control. This update changes strace to use the TRACE{FORK,VFORK,CLONE} ptrace capabilities which provide a cleaner, less error-prone interface to monitor and control process startup when tracing, thus preventing this bug. All users of strace are advised to upgrade to these updated packages, which fix this bug.

Commands:
14.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. Label files with the samba_share_t type to allow Samba to share them. Only label files you have created, and do not relabel system files with the samba_share_t type: Booleans can be enabled to share such files and directories. SELinux allows Samba to write to files labeled with the samba_share_t type, as long as the /etc/samba/smb.conf file and Linux permissions are set accordingly. The samba_etc_t type is used on certain files in the /etc/samba/ directory, such as smb.conf . Do not manually label files with the samba_etc_t type. If files in this directory are not labeled correctly, enter the restorecon -R -v /etc/samba command as the root user to restore such files to their default contexts. If /etc/samba/smb.conf is not labeled with the samba_etc_t type, starting the Samba service may fail and an SELinux denial message may be logged. The following is an example denial message when /etc/samba/smb.conf was labeled with the httpd_sys_content_t type:

Commands:
setroubleshoot: SELinux is preventing smbd (smbd_t) "read" to ./smb.conf (httpd_sys_content_t). For complete SELinux messages. run sealert -l deb33473-1069-482b-bb50-e4cd05ab18af