mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. The etcd service The etcd service is delivered as part of the Red Hat build of MicroShift RPM. The etcd service is run as a separate process and the etcd lifecycle is managed automatically by MicroShift. 1.1. Observe and debug the MicroShift etcd server You can gather journalctl logs to observe and debug the etcd server logs. Prerequisites The MicroShift service is running. Procedure To get the logs for etcd, run the following command: USD sudo journalctl -u microshift-etcd.scope Note MicroShift logs can be accessed separately from etcd logs using the journalctl -u microshift command. 1.2. Checking the etcd version You can get the version information for the etcd database included with your MicroShift by using one or both of the following methods, depending on the level of information that you need. Procedure To display the base database version information, run the following command: USD microshift-etcd version Example output microshift-etcd Version: 4.17.1 Base etcd Version: 3.5.13 To display the full database version information, run the following command: USD microshift-etcd version -o json Example output { "major": "4", "minor": "16", "gitVersion": "4.17.1~rc.1", "gitCommit": "140777711962eb4e0b765c39dfd325fb0abb3622", "gitTreeState": "clean", "buildDate": "2024-05-10T16:37:53Z", "goVersion": "go1.21.9" "compiler": "gc", "platform": "linux/amd64", "patch": "", "etcdVersion": "3.5.13" } 1.3. Troubleshooting etcd To troubleshoot etcd and improve performance, configure the memory allowance for the service. 1.4. Configuring the memoryLimitMB value to set parameters for the etcd server By default, etcd uses as much memory as necessary to handle the load on the system. In memory-constrained systems, you might need to limit the amount of memory etcd uses. Procedure Edit the /etc/microshift/config.yaml file to set the memoryLimitMB value. etcd: memoryLimitMB: 128 Note The minimum required value for memoryLimitMB on MicroShift is 128 MB. Values close to the minimum value are more likely to impact etcd performance. The lower the limit, the longer etcd takes to respond to queries. If the limit is too low or the etcd usage is high, queries time out. Verification After modifying the memoryLimitMB value in /etc/microshift/config.yaml , restart MicroShift by running the following command: USD sudo systemctl restart microshift Verify the new memoryLimitMB value is in use by running the following command: USD systemctl show --property=MemoryHigh microshift-etcd.scope

Commands:
sudo journalctl -u microshift-etcd.scope
microshift-etcd version
microshift-etcd Version: 4.17.1 Base etcd Version: 3.5.13
microshift-etcd version -o json
{ "major": "4", "minor": "16", "gitVersion": "4.17.1~rc.1", "gitCommit": "140777711962eb4e0b765c39dfd325fb0abb3622", "gitTreeState": "clean", "buildDate": "2024-05-10T16:37:53Z", "goVersion": "go1.21.9" "compiler": "gc", "platform": "linux/amd64", "patch": "", "etcdVersion": "3.5.13" }
etcd: memoryLimitMB: 128
sudo systemctl restart microshift
systemctl show --property=MemoryHigh microshift-etcd.scope
28.2.4. Enabling Remote Access with Telnet To enable remote access to a text mode installation, use the telnet option at the boot: prompt: You may then connect to the installation system with the telnet utility. The telnet command requires the name or IP address of the installation system: Warning To ensure the security of the installation process, only use the telnet option to install systems on networks with restricted access.

Commands:
linux text telnet
telnet computer.mydomain.com
5.8.5. Making Context Mounts Persistent To make context mounts persistent across remounting and reboots, add entries for the file systems in /etc/fstab or an automounter map, and use the desired context as a mount option. The following example adds an entry to /etc/fstab for an NFS context mount:

Commands:
server:/export /local/mount/ nfs context="system_u:object_r:httpd_sys_content_t:s0" 0 0
4.330. tuned 4.330.1. RHBA-2011:1176 - tuned bug fix update Updated tuned packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The "tuned" packages contain a daemon that tunes system settings dynamically. It does so by monitoring the usage of several system components periodically. Bug Fixes BZ# 695480 Previously, remote "tuned" service starts could have led to a service unresponsiveness under certain circumstances. With this update, the handling of stdin, stdout, or stderr during the service creation has been fixed to resolve this problem. BZ# 707079 Previously, using NIC bonding could have led to an unexpected termination of "tuned". With this update, the network device type determination has been fixed by handling more error conditions so that the aforementioned bug no longer occurs. All users of "tuned" are advised to upgrade to these updated packages, which fix these bugs.

Commands:
10.4. Configure 802.1Q VLAN Tagging Using the Command Line In Red Hat Enterprise Linux 7, the 8021q module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as root : To display information about the module, issue the following command: See the modprobe(8) man page for more command options. 10.4.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files Configure the parent interface in /etc/sysconfig/network-scripts/ifcfg- device_name , where device_name is the name of the interface: Configure the VLAN interface configuration in the /etc/sysconfig/network-scripts/ directory. The configuration file name should be the parent interface plus a . character plus the VLAN ID number. For example, if the VLAN ID is 192, and the parent interface is enp1s0 , then the configuration file name should be ifcfg-enp1s0.192 : If there is a need to configure a second VLAN, with for example, VLAN ID 193, on the same interface, enp1s0 , add a new file with the name enp1s0.193 with the VLAN configuration details. Restart the networking service in order for the changes to take effect. As root issue the following command: 10.4.2. Configure 802.1Q VLAN Tagging Using ip Commands To create an 802.1Q VLAN interface on Ethernet interface enp1s0 , with name VLAN8 and ID 8 , issue a command as root as follows: To view the VLAN, issue the following command: Note that the ip utility interprets the VLAN ID as a hexadecimal value if it is preceded by 0x and as an octal value if it has a leading 0 . This means that in order to assign a VLAN ID with a decimal value of 22 , you must not add any leading zeros. To remove the VLAN, issue a command as root as follows: To use multiple interfaces belonging to multiple VLANs, create locally enp1s0.1 and enp1s0.2 with the appropriate VLAN ID on top of a physical interface enp1s0 : Note that running a network sniffer on a physical device, you can capture the tagged frames reaching the physical device, even if no VLAN device is configured on top of enp1s0 . For example: Note VLAN interfaces created using ip commands at the command prompt will be lost if the system is shutdown or restarted. To configure VLAN interfaces to be persistent after a system restart, use ifcfg files. See Section 10.4.1, "Setting Up 802.1Q VLAN Tagging Using ifcfg Files"

Commands:
~]# modprobe --first-time 8021q modprobe: ERROR: could not insert '8021q': Module already in kernel
~]USD modinfo 8021q
DEVICE= interface_name TYPE=Ethernet BOOTPROTO=none ONBOOT=yes
DEVICE=enp1s0.192 BOOTPROTO=none ONBOOT=yes IPADDR=192.168.1.1 PREFIX=24 NETWORK=192.168.1.0 VLAN=yes
~]# systemctl restart network
~]# ip link add link enp1s0 name enp1s0.8 type vlan id 8
~]USD ip -d link show enp1s0.8 4: enp1s0.8@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT link/ether 52:54:00:ce:5f:6c brd ff:ff:ff:ff:ff:ff promiscuity 0 vlan protocol 802.1Q id 8 <REORDER_HDR>
~]# ip link delete enp1s0.8
~]# ip link add link enp1s0 name enp1s0.1 type vlan id 1 ip link set dev enp1s0.1 up ~]# ip link add link enp1s0 name enp1s0.2 type vlan id 2 ip link set dev enp1s0.2 up
tcpdump -nnei enp1s0 -vvv
22.13. Checking the Status of NTP To check if ntpd is configured to run at system start, issue the following command: By default, when ntpd is installed, it is configured to start at every system start. To check if ntpd is running, issue the following command: The command lists connected time servers and displays information indicating when they were last polled and the stability of the replies. The column headings are as follows: remote and refid: remote NTP server, and its NTP server st: stratum of server t: type of server (local, unicast, multicast, or broadcast) poll: how frequently to query server (in seconds) when: how long since last poll (in seconds) reach: octal bitmask of success or failure of last 8 queries (left-shifted); 377 = 11111111 = all recent queries were successful; 257 = 10101111 = 4 most recent were successful, 5 and 7 failed delay: network round trip time (in milliseconds) offset: difference between local clock and remote clock (in milliseconds) jitter: difference of successive time values from server (high jitter could be due to an unstable clock or, more likely, poor network performance) To obtain a brief status report from ntpd , issue the following command:

Commands:
~]USD chkconfig --list ntpd ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
~]USD ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +clock.util.phx2 .CDMA. 1 u 111 128 377 175.495 3.076 2.250 *clock02.util.ph .CDMA. 1 u 69 128 377 175.357 7.641 3.671 ms21.snowflakeh .STEP. 16 u - 1024 0 0.000 0.000 0.000 rs11.lvs.iif.hu .STEP. 16 u - 1024 0 0.000 0.000 0.000 2001:470:28:bde .STEP. 16 u - 1024 0 0.000 0.000 0.000
~]USD ntpstat unsynchronised time server re-starting polling server every 64 s
~]USD ntpstat synchronised to NTP server (10.5.26.10) at stratum 2 time correct to within 52 ms polling server every 1024 s
12.2. Assigning a PCI Device with virt-manager PCI devices can be added to guest virtual machines using the graphical virt-manager tool. The following procedure adds a Gigabit Ethernet controller to a guest virtual machine. Procedure 12.4. Assigning a PCI device to a guest virtual machine using virt-manager Open the hardware settings Open the guest virtual machine and click the Add Hardware button to add a new device to the virtual machine. Figure 12.1. The virtual machine hardware information window Select a PCI device Select PCI Host Device from the Hardware list on the left. Select an unused PCI device. Note that selecting PCI devices presently in use on the host causes errors. In this example, a spare 82576 network device is used. Click Finish to complete setup. Figure 12.2. The Add new virtual hardware wizard Add the new device The setup is complete and the guest virtual machine now has direct access to the PCI device. Figure 12.3. The virtual machine hardware information window

Commands:
Chapter 4. Known issues Red Hat build of OpenJDK 11 might include known issues. Solutions might exist for some of these known issues. XPath expressions Red Hat build of OpenJDK 11 specifies new default limits for XPath expressions. If you find that your code is exceeding these limits, you can raise them by passing the following parameters to your Red Hat build of OpenJDK deployment or by setting the JAVA_TOOL_OPTIONS environment variable to use them: -Djdk.xml.xpathExprGrpLimit, which defaults to 10 -Djdk.xml.xpathExprOpLimit, which defaults to 100 -Djdk.xml.xpathTotalOpLimit, which defaults to 10,000 These default limits restrict the number of expression groups, the number of operators in a single expression, and the total number of operators.

Commands:
5.4.13. Displaying Logical Volumes There are three commands you can use to display properties of LVM logical volumes: lvs , lvdisplay , and lvscan . The lvs command provides logical volume information in a configurable form, displaying one line per logical volume. The lvs command provides a great deal of format control, and is useful for scripting. For information on using the lvs command to customize your output, see Section 5.8, "Customized Reporting for LVM" . The lvdisplay command displays logical volume properties (such as size, layout, and mapping) in a fixed format. The following command shows the attributes of lvol2 in vg00 . If snapshot logical volumes have been created for this original logical volume, this command shows a list of all snapshot logical volumes and their status (active or inactive) as well. The lvscan command scans for all logical volumes in the system and lists them, as in the following example.

Commands:
lvdisplay -v /dev/vg00/lvol2
lvscan ACTIVE '/dev/vg0/gfslv' [1.46 GB] inherit
Chapter 7. Backing OpenShift Container Platform applications with OpenShift Data Foundation You cannot directly install OpenShift Data Foundation during the OpenShift Container Platform installation. However, you can install OpenShift Data Foundation on an existing OpenShift Container Platform by using the Operator Hub and then configure the OpenShift Container Platform applications to be backed by OpenShift Data Foundation. Prerequisites OpenShift Container Platform is installed and you have administrative access to OpenShift Web Console. OpenShift Data Foundation is installed and running in the openshift-storage namespace. Procedure In the OpenShift Web Console, perform one of the following: Click Workloads Deployments . In the Deployments page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop-down menu on the top right of the page. Click Workloads Deployment Configs . In the Deployment Configs page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment Config to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop-down menu on the top right of the page. In the Add Storage page, you can choose one of the following options: Click the Use existing claim option and select a suitable PVC from the drop-down list. Click the Create new claim option. Select the appropriate CephFS or RBD storage class from the Storage Class drop-down list. Provide a name for the Persistent Volume Claim. Select ReadWriteOnce (RWO) or ReadWriteMany (RWX) access mode. Note ReadOnlyMany (ROX) is deactivated as it is not supported. Select the size of the desired storage capacity. Note You can expand the block PVs but cannot reduce the storage capacity after the creation of Persistent Volume Claim. Specify the mount path and subpath (if required) for the mount path volume inside the container. Click Save . Verification steps Depending on your configuration, perform one of the following: Click Workloads Deployments . Click Workloads Deployment Configs . Set the Project as required. Click the deployment for which you added storage to display the deployment details. Scroll down to Volumes and verify that your deployment has a Type that matches the Persistent Volume Claim that you assigned. Click the Persistent Volume Claim name and verify the storage class name in the Persistent Volume Claim Overview page.

Commands:
Chapter 4. Accessing hosts Learn how to create a bastion host to access OpenShift Container Platform instances and access the control plane nodes with secure shell (SSH) access. 4.1. Accessing hosts on Amazon Web Services in an installer-provisioned infrastructure cluster The OpenShift Container Platform installer does not create any public IP addresses for any of the Amazon Elastic Compute Cloud (Amazon EC2) instances that it provisions for your OpenShift Container Platform cluster. To be able to SSH to your OpenShift Container Platform hosts, you must follow this procedure. Procedure Create a security group that allows SSH access into the virtual private cloud (VPC) created by the openshift-install command. Create an Amazon EC2 instance on one of the public subnets the installer created. Associate a public IP address with the Amazon EC2 instance that you created. Unlike with the OpenShift Container Platform installation, you should associate the Amazon EC2 instance you created with an SSH keypair. It does not matter what operating system you choose for this instance, as it will simply serve as an SSH bastion to bridge the internet into your OpenShift Container Platform cluster's VPC. The Amazon Machine Image (AMI) you use does matter. With Red Hat Enterprise Linux CoreOS (RHCOS), for example, you can provide keys via Ignition, like the installer does. After you provisioned your Amazon EC2 instance and can SSH into it, you must add the SSH key that you associated with your OpenShift Container Platform installation. This key can be different from the key for the bastion instance, but does not have to be. Note Direct SSH access is only recommended for disaster recovery. When the Kubernetes API is responsive, run privileged pods instead. Run oc get nodes , inspect the output, and choose one of the nodes that is a master. The hostname looks similar to ip-10-0-1-163.ec2.internal . From the bastion SSH host you manually deployed into Amazon EC2, SSH into that control plane host. Ensure that you use the same SSH key you specified during the installation: USD ssh -i <ssh-key-path> core@<master-hostname>

Commands:
ssh -i <ssh-key-path> core@<master-hostname>
5.107. indent 5.107.1. RHBA-2012:0753 - indent bug fix update An updated indent package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The indent package provides a utility to convert from one C writing style to a different one. Indent understands correct C syntax and can handle incorrect C syntax. Bug Fixes BZ# 733265 Prior to this update, suffixes were incorrectly separated when running the indent utility on code with decimal float constants. As a consequence, indent could encounter a compilation syntax error. This update modifies indent to understand decimal float suffixes as proposed by the N1312 draft of ISO/IEC WDTR24732. Now, indent handles decimal float constants as expected. BZ# 784304 Prior to this update, the internal test-suite did not signal test failure by exit code if indent failed to pass the test. This update adds an exit call with non-zero value to signal failure. All users of indent are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 1. Distinctions between automation hub and private automation hub Red Hat Ansible Automation Platform uses an automation hub as a central location for automation content that you can download and integrate into your Ansible automation. Two types of hubs are available: Automation hub Hosted by Red Hat on the Red Hat Hybrid Cloud Console , it contains only Red Hat supported or certified content. Private automation hub This is a self-hosted content management system. You can use it to access and manage all types of Ansible content and choose which Ansible content collections and versions are made available to your automation consumers. With a private automation hub, you can access these three types of content: Red Hat certified and supported content found in automation hub on the Red Hat Hybrid Cloud Console . Community content from Ansible Galaxy. Private content created and curated by an organization and shared locally.

Commands:
Chapter 29. Installing Without Media Important This procedure assumes you are already using Red Hat Enterprise Linux or another relatively modern Linux distribution, and the GRUB boot loader. It also assumes you are a somewhat experienced Linux user. This section discusses how to install Red Hat Enterprise Linux on your system without making any additional physical media. Instead, you can use your existing GRUB boot loader to start the installation program. 29.1. Retrieving Boot Files To perform an installation without media or a PXE server, your system must have two files stored locally, a kernel and an initial RAM disk. Copy the vmlinuz and initrd.img files from a Red Hat Enterprise Linux DVD (or DVD image) to the /boot/ directory, renaming them to vmlinuz-install and initrd.img-install . You must have root privileges to write files into the /boot/ directory.

Commands:
Chapter 6. Additional Resources This chapter provides references to other relevant sources of information about Red Hat Software Collections 3.7 and Red Hat Enterprise Linux. 6.1. Red Hat Product Documentation The following documents are directly or indirectly relevant to this book: Red Hat Software Collections 3.7 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Developer Toolset 10.1 Release Notes - The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection. Red Hat Developer Toolset 10.1 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Getting Started with Containers - This guide contains a comprehensive overview of information about building and using container images on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux Atomic Host. Using and Configuring Red Hat Subscription Manager - The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system. 6.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Software Collections on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands: