mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Uninstalling a cluster on Azure You can remove a cluster that you deployed to Microsoft Azure. 13.1. Removing a cluster that uses installer-provisioned infrastructure You can remove a cluster that uses installer-provisioned infrastructure from your cloud. Note After uninstallation, check your cloud provider for any resources not removed properly, especially with User Provisioned Infrastructure (UPI) clusters. There might be resources that the installer did not create or that the installer is unable to access. Prerequisites You have a copy of the installation program that you used to deploy the cluster. You have the files that the installation program generated when you created your cluster. Procedure From the directory that contains the installation program on the computer that you used to install the cluster, run the following command: USD ./openshift-install destroy cluster \ --dir <installation_directory> --log-level info 1 2 1 For <installation_directory> , specify the path to the directory that you stored the installation files in. 2 To view different details, specify warn , debug , or error instead of info . Note You must specify the directory that contains the cluster definition files for your cluster. The installation program requires the metadata.json file in this directory to delete the cluster. Optional: Delete the <installation_directory> directory and the OpenShift Container Platform installation program.

Commands:
./openshift-install destroy cluster --dir <installation_directory> --log-level info 1 2
3.7. RHBA-2011:1628 - new package: openslp A new openslp package is now available for Red Hat Enterprise Linux 6. OpenSLP is an open source implementation of the Service Location Protocol (SLP) which is an Internet Engineering Task Force (IETF) standards track protocol and provides a framework to allow networking applications to discover the existence, location, and configuration of networked services in enterprise networks. This enhancement update adds the openslp package to Red Hat Enterprise Linux 6. (BZ# 518286 ) All users who require OpenSLP are advised to install this new package.

Commands:
Chapter 24. Implementing Federation Warning Red Hat does not support federation at this time. This feature should only be used for testing, and should not be deployed in a production environment. 24.1. Federate with IdM using Red Hat Single Sign-On You can use Red Hat Single Sign-On (RH-SSO) to federate your IdM users for OpenStack authentication (authN). Federation allows your IdM users to login to the OpenStack Dashboard without revealing their credentials to any OpenStack services. Instead, when Dashboard needs a user's credentials, it will forward the user to Red Hat Single Sign-On (RH-SSO) and allow them to enter their IdM credentials there. As a result, RH-SSO asserts back to Dashboard that the user has successfully authenticated, and Dashboard then allows the user to access the project. In the diagram below, keystone (the SP) communicates with RH-SSO[id= the-federation-workflow_implementing-federation ] = The federation workflow This section describes how the Identity service (keystone), RH-SSO and IdM interact with each other. Federation in OpenStack uses the concept of Identity Providers and Service Providers: Identity Provider (IdP) - the service that stores the user accounts. In this case, the user accounts held in IdM, are presented to Keystone using RH-SSO. Service Provider (SP) - the service that requires authentication from the users in the IdP. In this case, keystone is the service provider that grants Dashboard access to IdM users. In the diagram below, keystone (the SP) communicates with RH-SSO (the IdP), which is also able to serve as a universal adapter for other IdPs. In this configuration, you can point keystone at RH-SSO, and RH-SSO will forward requests on to the Identity Providers that it supports (known as authentication modules), these currently include IdM and Active Directory. This is done by having the Service Provider (SP) and Identity Provider (IdP) exchange metadata, which each sysadmin then makes a decision to trust. The result is that the IdP can confidently make assertions, and the SP can then receive these assertions. Additional resources Federate with Identity Service

Commands:
8.9. Verifying a Configuration Once you have created your cluster configuration file, verify that it is running correctly by performing the following steps: At each node, restart the cluster software. That action ensures that any configuration additions that are checked only at startup time are included in the running configuration. You can restart the cluster software by running service cman restart . For example: Run service clvmd start , if CLVM is being used to create clustered volumes. For example: Run service gfs2 start , if you are using Red Hat GFS2. For example: Run service rgmanager start , if you using high-availability (HA) services. For example: At any cluster node, run cman_tool nodes to verify that the nodes are functioning as members in the cluster (signified as "M" in the status column, "Sts"). For example: At any node, using the clustat utility, verify that the HA services are running as expected. In addition, clustat displays status of the cluster nodes. For example: If the cluster is running as expected, you are done with creating a configuration file. You can manage the cluster with command-line tools described in Chapter 9, Managing Red Hat High Availability Add-On With Command Line Tools .

Commands:
service cman restart Stopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Waiting for corosync to shutdown: [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Starting gfs_controld... [ OK ] Unfencing self... [ OK ] Joining fence domain... [ OK ]
service clvmd start Activating VGs: [ OK ]
service gfs2 start Mounting GFS2 filesystem (/mnt/gfsA): [ OK ] Mounting GFS2 filesystem (/mnt/gfsB): [ OK ]
service rgmanager start Starting Cluster Service Manager: [ OK ]
cman_tool nodes Node Sts Inc Joined Name 1 M 548 2010-09-28 10:52:21 node-01.example.com 2 M 548 2010-09-28 10:52:21 node-02.example.com 3 M 544 2010-09-28 10:52:21 node-03.example.com
clustat Cluster Status for mycluster @ Wed Nov 17 05:40:00 2010 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ node-03.example.com 3 Online, rgmanager node-02.example.com 2 Online, rgmanager node-01.example.com 1 Online, Local, rgmanager Service Name Owner (Last) State ------- ---- ----- ------ ----- service:example_apache node-01.example.com started service:example_apache2 (none) disabled
Chapter 3. Bug fixes This part describes bugs fixed in Red Hat Satellite 6.15 that have a significant impact on users. Concurrency level setting Previously, the Concurrency level setting used in remote execution job scheduling did not always function properly. This could lead to the jobs being frozen until the service restart. With this release, this issue is now fixed and the Concurrency level setting works as intended. Jira:SAT-19794 Updating host facts now does not trigger the host_updated event Previously, updating host facts would trigger the host_updated event multiple times. This caused the subscribed webhooks to fire more than once on a single update of the host facts. With this release, updating the host facts does not trigger the host_updated event. If you want to be notified when host facts are updated, subscribe your webhooks to the new host_facts_updated event. This new event triggers the webhook only once with each update of the host facts. The host_updated event is still triggered if a user manually updates a host. Jira:SAT-20746 You can now access full details from webhook when removing a host Previously, only basic information about the host was available to the webhook template when you deleted a host. With this release, when you delete a host, the webhook template can access the full host details. Jira:SAT-20745 Registration exit code reflects registration failure Previously, the registration command returned the 0 exit code even when host registration failed. With this release, the registration command returns 0 only when it succeeds and non-zero codes otherwise. Bugzilla:2155444 Non-admin users can override Ansible variables Previously, Satellite users other than the System Administrator could not override Ansible variables even when they were assigned the Ansible Roles Manager user role. With this release, permissions have been corrected and non-admin users can override Ansible variables. Bugzilla:2181595 Generate host registration commands by using 0 as unlimited for JWT expiration Previously, it was not clear what value Hammer and API accept for generation of the host registration command with an unlimited authorization token. The accepted values are as follows: 0 means unlimited A value between 0 and 999999 is expiration in hours, 4 hours by default Other values are not accepted. With this release, the unlimited value has been clarified in the Hammer help and API reference. Bugzilla:2180568 Uploading an OpenSCAP report no longer fails on hosts that run RHEL 9.4 or later with FIPS mode enabled On Satellite hosts that run RHEL 9 in FIPS mode, uploading an OpenSCAP report previously failed with the following error: The problem has been addressed on the RHEL side and no longer affects Satellite hosts that run RHEL 9.4 or later. Note that uploading an OpenSCAP report in the described situation still fails on hosts that run RHEL 9.3 or earlier. See also Chapter 7, Known issues . Jira:SAT-22421

Commands:
Unable to load certs Neither PUB key nor PRIV key
B.84. samba B.84.1. RHSA-2010:0860 - Critical: samba security update Updated samba packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having critical security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Samba is a suite of programs used by machines to share files, printers, and other information. CVE-2010-3069 A missing array boundary checking flaw was found in the way Samba parsed the binary representation of Windows security identifiers (SIDs). A malicious client could send a specially-crafted SMB request to the Samba server, resulting in arbitrary code execution with the privileges of the Samba server (smbd). Users of Samba are advised to upgrade to these updated packages, which correct this issue. After installing this update, the smb service will be restarted automatically.

Commands:
5.9.3.2.3. Issuing the df Command While using /etc/mtab or /proc/mounts lets you know what file systems are currently mounted, it does little beyond that. Most of the time you are more interested in one particular aspect of the file systems that are currently mounted -- the amount of free space on them. For this, we can use the df command. Here is some sample output from df : Several differences from /etc/mtab and /proc/mount are immediately obvious: An easy-to-read heading is displayed With the exception of the shared memory file system, only disk-based file systems are shown Total size, used space, free space, and percentage in use figures are displayed That last point is probably the most important because every system administrator eventually has to deal with a system that has run out of free disk space. With df it is very easy to see where the problem lies.

Commands:
Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda3 8428196 4280980 3719084 54% / /dev/sda1 124427 18815 99188 16% /boot /dev/sda4 8428196 4094232 3905832 52% /home none 644600 0 644600 0% /dev/shm
Power Monitoring OpenShift Container Platform 4.18 Configuring and using power monitoring for OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: port: 9103 1 nodeSelector: kubernetes.io/os: linux 2 Tolerations: 3 - key: "" operator: "Exists" value: "" effect: ""
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler status: exporter: conditions: 1 - lastTransitionTime: '2024-01-11T11:07:39Z' message: Reconcile succeeded observedGeneration: 1 reason: ReconcileSuccess status: 'True' type: Reconciled - lastTransitionTime: '2024-01-11T11:07:39Z' message: >- Kepler daemonset "kepler-operator/kepler" is deployed to all nodes and available; ready 2/2 observedGeneration: 1 reason: DaemonSetReady status: 'True' type: Available currentNumberScheduled: 2 2 desiredNumberScheduled: 2 3
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: redfish: secretRef: <secret_name> required 1 probeInterval: 60s 2 skipSSLVerify: false 3
<your_kubelet_node_name>,<redfish_username>,<redfish_password>,https://<redfish_ip_or_hostname>/
control-plane,exampleuser,examplepass,https://redfish.nodes.example.com worker-1,exampleuser,examplepass,https://redfish.nodes.example.com worker-2,exampleuser,examplepass,https://another.redfish.nodes.example.com
oc -n openshift-power-monitoring create secret generic redfish-secret --from-file=redfish.csv
apiVersion: v1 kind: Secret metadata: name: redfish-secret data: redfish.csv: YmFyCg== #
Chapter 7. Known issues This part describes known issues in Red Hat Satellite 6.15. When using satellite-maintain backup on Capsule Server, the certificate tar file is not collected The satellite-maintain backup command does not collect the certificate tar file of the Capsule Server when creating a backup. As a result, restoring the archive fails. To work around this problem, re-generate the certificate tar file from the Satellite Server. Jira:SAT-23881 Disabled Puppet with all data removed cannot be re-enabled If the Puppet plug-in was disabled with the -f, --remove-all-data argument and you attempt to enable it again, Satellite maintain fails. Bugzilla:2087067 External databases require hstore extension for upgrade and installation If you use an external database: You will have to install the postgresql-contrib package and create the hstore extension in PostgreSQL prior to upgrading to 6.15. You will have to install the postgresql-contrib package and create the hstore extension prior to installing a new Satellite 6.15. If the extension is not manually created, upgrade or installation will end in an error: If you see this error, install the postgresql-contrib package and create the hstore extension prior to continuing. For more information, see Installing PostgreSQL in Installing Satellite Server in a connected network environment and Upgrading a Connected Satellite Server in Upgrading connected Red Hat Satellite to 6.15 . Jira:SAT-21163 Web UI sometimes displays names of hosts as FQDNs when Display FQDN for hosts is disabled The Display FQDN for hosts setting is applied inconsistently in the Satellite web UI. Some pages in the web UI display names of hosts as FQDNs even when Display FQDN for hosts is disabled. Jira:SAT-22241

Commands:
permission denied to create extension "hstore"
Chapter 8. Creating an OAuth application in GitHub You can authorize your Red Hat Quay registry to access a GitHub account and its repositories by registering it as a GitHub OAuth application. 8.1. Create new GitHub application Use the following procedure to create an OAuth application in Github. Procedure Log into Github Enterprise. In the navigation pane, select your username Your organizations . In the navigation pane, select Applications . Click Register New Application . The Register a new OAuth application configuration screen is displayed, for example: Enter a name for the application in the Application name textbox. In the Homepage URL textbox, enter your Red Hat Quay URL. Note If you are using public GitHub, the Homepage URL entered must be accessible by your users. It can still be an internal URL. In the Authorization callback URL , enter https://<RED_HAT_QUAY_URL>/oauth2/github/callback . Click Register application to save your settings. When the new application's summary is shown, record the Client ID and the Client Secret shown for the new application.

Commands:
Chapter 4. Overriding the cluster-wide default node selector for OpenShift Data Foundation post deployment When a cluster-wide default node selector is used for OpenShift Data Foundation, the pods generated by CSI daemonsets are able to start only on the nodes that match the selector. To be able to use OpenShift Data Foundation from nodes which do not match the selector, override the cluster-wide default node selector by performing the following steps in the command line interface : Procedure Specify a blank node selector for the openshift-storage namespace. Delete the original pods generated by the DaemonSets.

Commands:
oc annotate namespace openshift-storage openshift.io/node-selector=
delete pod -l app=csi-cephfsplugin -n openshift-storage delete pod -l app=csi-rbdplugin -n openshift-storage
28.5. Changing Password Expiration Date with Immediate Effect You can use the ipa user-mod or ldapmodify utilities to change the expiration date of a user password. Changing the expiration date of a user password by using the ipa user-mod utility To enforce an immediate change of the expiration date, use ipa user-mod command with the --password-expiration option. For example, to set the expiration date to 2016-02-03 20:37:34 in the UTC time zone, run: Note that the command uses a generalized time format and setting the expiration date to 20160203203734Z is also possible. Changing the expiration date of a user password by using the ldapmodify utility To enforce an immediate change of the expiration date, reset the krbPasswordExpiration attribute value in LDAP. To change the expiration date for a single user: Set the new value for the krbPasswordExpiration attribute for the user entry by using the following command: The krbPasswordExpiration format follows generalized time format YYYMMDDHHMMSS.0Z. Press Ctrl + D to confirm and send the changes to the server. To edit multiple entries at once, use ldapmodify with the -f option to reference an LDIF file.

Commands:
ipa user-mod user_name --password-expiration='2016-02-03 20:37:34Z'
ldapmodify -D "cn=Directory Manager" -w secret -h server.example.com -p 389 -vv dn: uid= user_name ,cn=users,cn=accounts,dc= example ,dc= com changetype: modify replace: krbPasswordExpiration krbPasswordExpiration: 20160203203734Z
Chapter 4. Management 4.1. Browsing Broker Information Now that you've populated the inventory with details about your AMQ 7 Server, you can browse information about most aspects of your AMQ Broker instances. To view details about AMQ 7 Servers, perform the following steps: Click Resources > Servers - Top Level Imports to view the AMQ 7 Server in the Servers - Top Level Imports window. Double-click the AMQ 7 Server entry. The left navigation pane now displays the AMQ Server and the areas into which you can drill down to view detailed data about your message brokers, acceptors, addresses, and more. With each level you drill down into the hierarchy, the main window displays detailed information specific to the AMQ Server you selected. In addition, the main window includes a set of tabs such as Summary, Inventory, Alerts, Monitoring, and Events that you can use to view different aspects of the entities you've selected on the left. 4.2. Managing Brokers You can perform myriad monitoring, deployment, and management operations by using JON. It's strongly recommended that you browse the JON guide titled Using JBoss Operations Network for Monitoring, Deploying, and Managing Resources to ensure that you're taking advantage of all the benefits that JON has to offer. Related information Using JBoss Operations Network for Monitoring, Deploying, and Managing Resources

Commands:
4.2. Networking Mellanox SR-IOV Support Single Root I/O Virtualization (SR-IOV) is now supported as a Technology Preview in the Mellanox libmlx4 library and the following drivers: mlx_core mlx4_ib (InfiniBand protocol) mlx_en (Ethernet protocol) Package: kernel-2.6.32-554 Open multicast ping (Omping), BZ# 657370 Open Multicast Ping (Omping) is a tool to test the IP multicast functionality, primarily in the local network. This utility allows users to test IP multicast functionality and assists in the diagnosing if an issues is in the network configuration or elsewhere (that is, a bug). In Red Hat Enterprise Linux 6 Omping is provided as a Technology Preview. Package: omping-0.0.4-1 QFQ queuing discipline In Red Hat Enterprise Linux 6, the tc utility has been updated to work with the Quick Fair Scheduler (QFQ) kernel features. Users can now take advantage of the new QFQ traffic queuing discipline from userspace. This feature is considered a Technology Preview. Package: kernel-2.6.32-554 vios-proxy, BZ# 721119 vios-proxy is a stream-socket proxy for providing connectivity between a client on a virtual guest and a server on a Hypervisor host. Communication occurs over virtio-serial links. Package: vios-proxy-0.2-1 Support for Intel X710 and XL710 family Ethernet adapters Red Hat Enterprise Linux 6.7 adds the i40e and i40evf kernel drivers, which enable support for Intel X710 and XL710 family Ethernet adapters. These drivers are provided only as a Technology Preview.

Commands:
B.2.3. Other Connectivity Errors Unable to connect to server at server:port : Connection refused The daemon is not running on the server or is configured not to listen, using configuration option listen_tcp or listen_tls . End of file while reading data: nc: using stream socket: Input/output error If you specified ssh transport, the daemon is likely not running on the server. Solve this error by verifying that the daemon is running on the server.

Commands:
Appendix B. Revision History Revision History Revision 1.0-22 Thu May 23 2019 Jiri Herrmann Version for 7.7 Beta publication Revision 1.0-21 Thu Oct 25 2018 Jiri Herrmann Version for 7.6 GA publication Revision 1.0-21 Thu Aug 14 2018 Jiri Herrmann Version for 7.6 Beta publication Revision 1.0-20 Thu Apr 5 2018 Jiri Herrmann Version for 7.5 GA publication Revision 1.0-18 Thu Jul 27 2017 Jiri Herrmann Version for 7.4 GA publication Revision 1.0-15 Mon Oct 17 2016 Jiri Herrmann Version for 7.3 GA publication Revision 1.0-9 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 1.0-8 Wed Feb 18 2015 Scott Radvan Version for 7.1 GA release.

Commands:
3.2.3. Example Usage Example 3.2. Limiting CPU access The following examples assume you have an existing hierarchy of cgroups configured and the cpu subsystem mounted on your system: To allow one cgroup to use 25% of a single CPU and a different cgroup to use 75% of that same CPU, use the following commands: To limit a cgroup to fully utilize a single CPU, use the following commands: To limit a cgroup to utilize 10% of a single CPU, use the following commands: On a multi-core system, to allow a cgroup to fully utilize two CPU cores, use the following commands:

Commands:
~]# echo 250 > /cgroup/cpu/blue/cpu.shares ~]# echo 750 > /cgroup/cpu/red/cpu.shares
~]# echo 10000 > /cgroup/cpu/red/cpu.cfs_quota_us ~]# echo 10000 > /cgroup/cpu/red/cpu.cfs_period_us
~]# echo 10000 > /cgroup/cpu/red/cpu.cfs_quota_us ~]# echo 100000 > /cgroup/cpu/red/cpu.cfs_period_us
~]# echo 200000 > /cgroup/cpu/red/cpu.cfs_quota_us ~]# echo 100000 > /cgroup/cpu/red/cpu.cfs_period_us