mtpti5iD/redhat-docs_dataset huggingface dataset:
7.170. pykickstart 7.170.1. RHBA-2015:1296 - pykickstart bug fix and enhancement update An updated pykickstart package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. The pykickstart package contains a Python library for manipulating Kickstart files. Bug Fix BZ# 995443 Previously, the pykickstart utility did not enforce using both the "--size=" and "--grow=" options at the same time, which was required by anaconda. As a consequence, the installation failed to complete and the following misleading error message was returned: ERROR : Unable to create new logical volume with no extents With this update, pykickstart enforces using both "--size=" and "--grow=" at the same time, and, if the installation fails, displays a clear message that the kickstart file needs to be modified. Enhancements BZ# 1017061 This update fixes a typographical error in an error message returned when using the "autopart" and "part" utilities at the same time. BZ# 1182624 The "clearpart" command now supports the "--cdl" option that instructs anaconda to reformat any Linux Disk Layout Direct Access Storage Devices (LDL DASDs) to the Compatible Disk Layout (CDL) format. This option is only useful on the System z platform. All pykickstart users are advised to upgrade to this updated package, which fixes this bug and adds these enhancements.

Commands:
Chapter 1. Overview Troubleshooting OpenShift Data Foundation is written to help administrators understand how to troubleshoot and fix their Red Hat OpenShift Data Foundation cluster. Most troubleshooting tasks focus on either a fix or a workaround. This document is divided into chapters based on the errors that an administrator may encounter: Chapter 2, Downloading log files and diagnostic information using must-gather shows you how to use the must-gather utility in OpenShift Data Foundation. Chapter 4, Commonly required logs for troubleshooting shows you how to obtain commonly required log files for OpenShift Data Foundation. Chapter 7, Troubleshooting alerts and errors in OpenShift Data Foundation shows you how to identify the encountered error and perform required actions. Warning Red Hat does not support running Ceph commands in OpenShift Data Foundation clusters (unless indicated by Red Hat support or Red Hat documentation) as it can cause data loss if you run the wrong commands. In that case, the Red Hat support team is only able to provide commercially reasonable effort and may not be able to restore all the data in case of any data loss. 16include::_artifacts/global-attributes.adoc[]

Commands:
Chapter 5. Creating a basic cluster on Red Hat OpenStack Platform This procedure creates a high availability cluster on an RHOSP platform with no fencing or resources configured. Prerequisites An RHOSP instance is configured for each HA cluster node The HAcluster node is running RHEL 9.1 or later High Availability and RHOSP packages are installed on each node, as described in Installing the high availability and RHOSP packages and agents . Procedure On one of the cluster nodes, enter the following command to authenticate the pcs user hacluster . Specify the name of each node in the cluster. In this example, the nodes for the cluster are node01 , node02 , and node03 . Create the cluster. In this example, the cluster is named newcluster . Verification Enable the cluster. Start the cluster. The command's output indicates whether the cluster has started on each node.

Commands:
pcs host auth node01 node02 node03 Username: hacluster Password: node01: Authorized node02: Authorized node03: Authorized
pcs cluster setup newcluster node01 node02 node03 Synchronizing pcsd certificates on nodes node01, node02, node03... node02: Success node03: Success node01: Success Restarting pcsd on the nodes in order to reload the certificates... node02: Success node03: Success node01: Success
pcs cluster enable --all node01: Cluster Enabled node02: Cluster Enabled node03: Cluster Enabled
pcs cluster start --all node02: Starting Cluster... node03: Starting Cluster... node01: Starting Cluster
Chapter 10. Authentication and Interoperability Updating a machine account password with adcli in some cases fails with SELinux error When attempting to update the machine account password using the adcli tool in Red Hat Enterprise Linux 6.10, the system security services daemon (SSSD) sometimes tries to update an internal Samba database that contains also the machine account password. As a consequence, the SELinux access vector cache (AVC) states that SSSD and its subprocesses are not allowed to run Samba's net command to update the internal Samba database. To work around this problem, you can add a local SELinux policy by creating a sssd_samba.te file with the following content: And then enter the following commands: As a result, SSSD with adcli can update Samba's internal database without an SELinux AVC error. (BZ# 1558428 ) AD users cannot use sudo on IdM hosts if default_domain_suffix is set In a trust between Identity Management (IdM) and Active Directory (AD), AD users cannot run sudo commands on IdM hosts if the default_domain_suffix parameter in the /etc/sssd/sssd.conf file is set to the AD domain. To work around the problem, remove the default_domain_suffix parameter from the /etc/sssd/sssd.conf file. As a result, sudo policies work as expected both for AD and IdM users. Note that after you remove the default_domain_suffix parameter, AD users must use user_name@domain_name instead of the short version of their user name to log in. (BZ# 1550192 )

Commands:
module sssd_samba 1.0; require { type sssd_t; type samba_net_exec_t; class file execute; } #============= sssd_t ============== allow sssd_t samba_net_exec_t:file execute;
yum install selinux-policy-devel make -f /usr/share/selinux/devel/Makefile sssd_samba.pp semodule -i sssd_samba.pp
B.16.3. RHSA-2011:0428 - Important: dhcp security update Updated dhcp packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. CVE-2011-0997 It was discovered that the DHCP client daemon, dhclient, did not sufficiently sanitize certain options provided in DHCP server replies, such as the client hostname. A malicious DHCP server could send such an option with a specially-crafted value to a DHCP client. If this option's value was saved on the client system, and then later insecurely evaluated by a process that assumes the option is trusted, it could lead to arbitrary code execution with the privileges of that process. Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue. All dhclient users should upgrade to these updated packages, which contain a backported patch to correct this issue.

Commands:
13.2. Prepackaged Scripts Red Hat provides scripts to export Samba (SMB) share when you start a volume and to remove the share when you stop the volume. These scripts are available at: /var/lib/glusterd/hooks/1/start/post and /var/lib/glusterd/hooks/1/stop/pre . By default, the scripts are enabled. When you start a volume using the following command: # gluster volume start VOLNAME The S30samba-start.sh script performs the following: Adds Samba share configuration details of the volume to the smb.conf file Mounts the volume through FUSE and adds an entry in /etc/fstab for the same. Restarts Samba to run with updated configuration When you stop the volume using the following command: # gluster volume stop VOLNAME The S30samba-stop.sh script performs the following: Removes the Samba share details of the volume from the smb.conf file Unmounts the FUSE mount point and removes the corresponding entry in /etc/fstab Restarts Samba to run with updated configuration

Commands:
Chapter 14. Configuring the systemd journal by using RHEL system roles With the journald RHEL system role you can automate the systemd journal, and configure persistent logging by using the Red Hat Ansible Automation Platform. 14.1. Configuring persistent logging by using the journald RHEL system role By default, the systemd journal stores logs only in a small ring buffer in /run/log/journal , which is not persistent. Rebooting the system also removes journal database logs. You can configure persistent logging consistently on multiple systems by using the journald RHEL system role. Prerequisites You have prepared the control node and the managed nodes . You are logged in to the control node as a user who can run playbooks on the managed nodes. The account you use to connect to the managed nodes has sudo permissions on them. Procedure Create a playbook file, for example ~/playbook.yml , with the following content: --- - name: Configure journald hosts: managed-node-01.example.com tasks: - name: Configure persistent logging ansible.builtin.include_role: name: rhel-system-roles.journald vars: journald_persistent: true journald_max_disk_size: <size> journald_per_user: true journald_sync_interval: <interval> The settings specified in the example playbook include the following: journald_persistent: true Enables persistent logging. journald_max_disk_size: <size> Specifies the maximum size of disk space for journal files in MB, for example, 2048 . journald_per_user: true Configures journald to keep log data separate for each user. journald_sync_interval: <interval> Sets the synchronization interval in minutes, for example, 1 . For details about all variables used in the playbook, see the /usr/share/ansible/roles/rhel-system-roles.journald/README.md file on the control node. Validate the playbook syntax: Note that this command only validates the syntax and does not protect against a wrong but valid configuration. Run the playbook: Additional resources /usr/share/ansible/roles/rhel-system-roles.journald/README.md file /usr/share/doc/rhel-system-roles/journald/ directory

Commands:
--- - name: Configure journald hosts: managed-node-01.example.com tasks: - name: Configure persistent logging ansible.builtin.include_role: name: rhel-system-roles.journald vars: journald_persistent: true journald_max_disk_size: <size> journald_per_user: true journald_sync_interval: <interval>
ansible-playbook --syntax-check ~/playbook.yml
ansible-playbook ~/playbook.yml
4.12.3. Dovecot 4.12.3.1. Dovecot configuration The configuration for Dovecot 2.x has changed. The master configuration file /etc/dovecot.conf has moved to /etc/dovecot/dovecot.conf and other parts of Dovecot configuration have moved to /etc/dovecot/conf.d/*.conf . The majority of the configuration is the same and is compatible with this new version; however, you can test your configuration and list which options have been renamed, removed, or otherwise changed in this new version with the following command:

Commands:
doveconf [-n] -c /old/dovecot.conf
B.2.3. Configuration File Changes Because RPM performs intelligent upgrading of packages with configuration files, you may see one or the other of the following messages: This message means that changes you made to the configuration file may not be forward-compatible with the new configuration file in the package, so RPM saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible, to ensure that your system continues to function properly. Alternatively, RPM may save the package's new configuration file as, for example, foo.conf.rpmnew , and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one with a diff program. If you attempt to upgrade to a package with an older version number (that is, if a higher version of the package is already installed), the output is similar to the following: To force RPM to upgrade anyway, use the --oldpackage option:

Commands:
saving /etc/foo.conf as /etc/foo.conf.rpmsave
package foo-2.0-1.el6.x86_64.rpm (which is newer than foo-1.0-1) is already installed
-Uvh --oldpackage foo-1.0-1.el6.x86_64.rpm
Appendix B. List of tickets by component Bugzilla and JIRA tickets are listed in this document for reference. The links lead to the release notes in this document that describe the tickets. Component Tickets API Jira:SAT-28134 , Jira:SAT-28135 Authentication Jira:SAT-18360 Backup & Restore Jira:SAT-20955 , Jira:SAT-23093 Capsule - Content Jira:SAT-16330 Compute Resources - VMWare Jira:SAT-21075 , Jira:SAT-23052 Container Management - Content Jira:SAT-20280 , Jira:SAT-23852 Content Views Jira:SAT-20281 Content management Jira:SAT-27936 Discovery Image Jira:SAT-24197 Hammer Jira:SAT-28136 , Jira:SAT-28141 , Jira:SAT-28367 Host management Jira:SAT-16036 Installation Jira:SAT-24140 , Jira:SAT-24414 , Jira:SAT-27979 Provisioning Jira:SAT-26071 , Jira:SAT-23034 , Jira:SAT-21075 , Jira:SAT-24654 , Jira:SAT-18663 , Jira:SAT-21012 Provisioning Templates Jira:SAT-23053 , Jira:SAT-25042 , Jira:SAT-23943 Pulp Jira:SAT-27979 Registration Jira:SAT-18615 , Jira:SAT-23536 , Jira:SAT-21682 , Jira:SAT-23047 Repositories Jira:SAT-25511 , Jira:SAT-29303 , Jira:SAT-28387 SCAP Plugin Jira:SAT-22421 , Jira:SAT-28297 Satellite Maintain Jira:SAT-21970 Security Jira:SAT-23806 Upgrades Jira:SAT-21970 , Jira:SAT-23369 , Jira:SAT-24414 Users & Roles Jira:SAT-28731 Web UI Jira:SAT-23240 , Jira:SAT-11630 , Jira:SAT-21815 , Jira:SAT-17785 , Jira:SAT-23211 , Jira:SAT-21887 , Jira:SAT-18270 , Jira:SAT-23947 , Jira:SAT-20041 , Jira:SAT-18427 other Jira:SAT-23536 , Jira:SAT-28136 , Jira:SAT-28134 , Jira:SAT-28141 , Jira:SAT-28135 , Jira:SAT-28820 , Jira:SAT-28367 , Jira:SAT-21137 , Jira:SAT-21372 , Jira:SAT-28297

Commands:
4.3. Additional Resources While programs allowing users to gain administrative privileges are a potential security risk, security itself is beyond the scope of this particular book. You should therefore see sources listed below for more information regarding security and privileged access. Installed Documentation su (1) - the manual page for su provides information regarding the options available with this command. sudo (8) - the manual page for sudo includes a detailed description of this command as well as a list of options available for customizing sudo 's behavior. pam (8) - the manual page describing the use of Pluggable Authentication Modules for Linux. Online Documentation Red Hat Enterprise Linux 6 Security Guide - The Security Guide describes in detail security risks and mitigating techniques related to programs for gaining privileges. Red Hat Enterprise Linux 6 Managing Single Sign-On and Smart Cards - This guide provides, among other things, a detailed description of Pluggable Authentication Modules (PAM) , their configuration and usage.

Commands:
17.11. Device Aliases Device aliases are virtual devices associated with the same physical hardware, but they can be activated at the same time to have different IP addresses. They are commonly represented as the device name followed by a colon and a number (for example, eth0:1). They are useful if you want to have multiple IP addresses for a system that only has one network card. After configuring the Ethernet device -such as eth0 -to use a static IP address (DHCP does not work with aliases), go to the Devices tab and click New . Select the Ethernet card to configure with an alias, set the static IP address for the alias, and click Apply to create it. Since a device already exists for the Ethernet card, the one just created is the alias, such as eth0:1 . Warning If you are configuring an Ethernet device to have an alias, neither the device nor the alias can be configured to use DHCP. You must configure the IP addresses manually. Figure 17.18, "Network Device Alias Example" shows an example of one alias for the eth0 device. Notice the eth0:1 device - the first alias for eth0 . The second alias for eth0 would have the device name eth0:2 , and so on. To modify the settings for the device alias, such as whether to activate it at boot time and the alias number, select it from the list and click the Edit button. Figure 17.18. Network Device Alias Example Select the alias and click the Activate button to activate the alias. If you have configured multiple profiles, select which profiles in which to include it. To verify that the alias has been activated, use the command /sbin/ifconfig . The output should show the device and the device alias with different IP addresses:

Commands:
eth0 Link encap:Ethernet HWaddr 00:A0:CC:60:B7:G4 inet addr:192.168.100.5 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:161930 errors:1 dropped:0 overruns:0 frame:0 TX packets:244570 errors:0 dropped:0 overruns:0 carrier:0 collisions:475 txqueuelen:100 RX bytes:55075551 (52.5 Mb) TX bytes:178108895 (169.8 Mb) Interrupt:10 Base address:0x9000 eth0:1 Link encap:Ethernet HWaddr 00:A0:CC:60:B7:G4 inet addr:192.168.100.42 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:10 Base address:0x9000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5998 errors:0 dropped:0 overruns:0 frame:0 TX packets:5998 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1627579 (1.5 Mb) TX bytes:1627579 (1.5 Mb)
Chapter 4. Executing tasks using Red Hat Insights You can execute tasks on remote systems in the Red Hat Hybrid Cloud Console directly from Red Hat Insights Tasks. Tasks you can execute are: RHEL pre-upgrade analysis utility tasks. Pre-conversion analysis utility tasks. Convert to RHEL from CentOS Linux 7. Note Prerequisites and actions required to execute specific Insights tasks will vary. Here are general instructions to execute a task. Prerequisites You are logged in to the Red Hat Hybrid Cloud Console. You are a member of a User Access group with the Tasks administrator role. You have connected systems and addressed dependencies for Remote Host Configuration (rhc), rhc-worker-playbook and ansible-core , as needed. See Enabling host communication with Insights in the Red Hat Insights Remediations Guide . You have addressed dependencies for Satellite 6.11+. See Enabling host communication with Insights in the Red Hat Insights Remediations Guide. Services in the Insights Automation Toolkit have similar dependency requirements that must be met before Red Hat Insights users can execute playbooks for remediations and tasks. Procedure Navigate to Automation Toolkit > Tasks . Select a task to execute and click Run Task . Optional: Edit the default task name to customize it for your needs. Note After you execute the task, you will not be able to change the task name again. Make note of any task-specific prerequisites shown in the brief description of the task. Select the systems on which to execute the task. You can use filters to search and filter systems by: Name Operating System Tag Click Execute task . The task executes on the selected systems. You might see a pop-up that shows that your task is running. Click View Progress to view the task details page which shows how the task is executing on each of your selected systems. Review Status and Message details. If shown, click the Show more icon beside the system name to find more information about messages. Click Tasks to go to the task detail view to see more information about how the task executed on the selected systems. Click the Activity tab to see the status of all the task you have executed. Tasks are in chronological order, by the most recent date and time. Note A Completed status indicates that the task executed, but does not indicate that the task accomplished its goal. Optional: Click the task you executed to return to the task detail view to see more information about how the task executed on the selected systems. Steps You might need to resolve errors, such as an error that occurs because you need to install a software package on your systems before a task can successfully execute. After you resolve those errors, you can execute the task again on the same systems. Optional: To execute a task again, click Run Task again. The previously selected systems are still selected, and you can also add additional systems, if needed.

Commands:
1.2. Storage Array Support By default, DM-Multipath includes support for the most common storage arrays that support DM-Multipath. The supported devices can be found in the multipath.conf.defaults file. If your storage array supports DM-Multipath and is not configured by default in this file, you may need to add them to the DM-Multipath configuration file, multipath.conf . For information on the DM-Multipath configuration file, see Chapter 4, The DM-Multipath Configuration File . Some storage arrays require special handling of I/O errors and path switching. These require separate hardware handler kernel modules.

Commands:
4.367. zlib 4.367.1. RHBA-2011:0931 - zlib bug fix update Updated zlib packages that fix one bug are now available for Red Hat Enterprise Linux 6. The zlib package provides a general-purpose lossless data compression library that is used by many different programs. Bug Fix BZ# 622781 When used to combine two Adler-32 checksums, the adler32_combine() function could have produced an incorrect result under certain circumstances. With this update, the underlying algorithm has been fixed, and the adler32_combine() function no longer returns incorrect checksums. All users of zlib are advised to upgrade to these updated packages, which fix this bug. 4.367.2. RHEA-2011:1678 - zlib enhancement update Enhanced zlib packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The zlib package provides a general-purpose lossless data compression library that is used by many different programs. Enhancement BZ# 727288 This update sets RELRO flags by default, so that the zlib library is compiled with partial RELRO protection support. All users of zlib are advised to upgrade to these updated packages, which add this enhancement.

Commands:
8.162. oprofile 8.162.1. RHEA-2014:1473 - oprofile bug fix and enhancement update An updated oprofile package that fix several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. OProfile is a system-wide profiler for Linux systems. The profiling runs transparently in the background and profile data can be collected at any time. OProfile uses the hardware performance counters provided on many processors, and can use the Real Time Clock (RTC) for profiling on processors without counters. Note The oprofile package has been upgraded to upstream version 0.9.9, which provides a number of bug fixes and enhancements over the version including added support for Intel Xeon Processor E5-XXXX v2, Intel Xeon Processor E3-XXXX v3, Intel Broadwell Microarchitecture and Intel Atom Processor CXXXX CPU architectures. (BZ# 809709 , BZ# 818353 , BZ# 832160 , BZ# 1121437 , BZ# 1128627 ) Users of oprofile are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: