Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Assessing and remediating system issues by using Red Hat Lightspeed tasks
Use predefined playbooks provided by the Red Hat Lightspeed tasks service to resolve issues on your systems
Abstract
Chapter 1. Overview of Red Hat Lightspeed tasks
In Red Hat Lightspeed, the Tasks feature offers predefined playbooks that help you maintain the health of your infrastructure by simplifying and solving complex problems by using automated tasks. Red Hat Lightspeed tasks solve specific problems and are typically run once on your systems to accomplish things such as detecting a high-profile vulnerability on your systems or preparing systems for a major upgrade. You can find tasks in Red Hat Hybrid Cloud Console > Red Hat Lightspeed > RHEL > Automation Toolkit > Tasks in the Red Hat Lightspeed UI.
Red Hat Lightspeed anticipates your need to solve problems and get things done in your infrastructure, and continuously adds specific tasks to the Automation Toolkit.
The pre-built tasks that you can run in Red Hat Lightspeed include:
-
Run the Red Hat Lightspeed client (
insights-client) - Run the Ansible ping module
- Pre-conversion analysis for converting to RHEL
- Convert to RHEL from CentOS Linux 7
- Pre-upgrade analysis for in-place upgrade from RHEL 8
- Initiate update of image mode for RHEL host
- Initiate update of RHEL AI host
To get started with running tasks in Red Hat Lightspeed, review the following important information:
- User Access settings in the Red Hat Hybrid Cloud Console. Find out what role or level of user access you need to complete tasks.
- Registering and connecting systems to Red Hat Lightspeed to run tasks. Using tasks requires you to register and connect systems to Red Hat Lightspeed.
- Running tasks by using Red Hat Lightspeed. Understand how to find and run tasks.
The system requirements to run different tasks can vary.
1.1. User Access settings in the Red Hat Hybrid Cloud Console
User Access is the Red Hat implementation of role-based access control (RBAC). Your Organization Administrator uses User Access to configure what users can see and do on the Red Hat Hybrid Cloud Console (the console):
- Control user access by organizing roles instead of assigning permissions individually to users.
- Create groups that include roles and their corresponding permissions.
- Assign users to these groups, allowing them to inherit the permissions associated with their group’s roles.
1.1.1. Predefined User Access groups and roles
To make groups and roles easier to manage, Red Hat provides two predefined groups and a set of predefined roles:
Predefined groups
The Default access group contains all users in your organization. Many predefined roles are assigned to this group. It is automatically updated by Red Hat.
NoteIf the Organization Administrator makes changes to the Default access group its name changes to Custom default access group and it is no longer updated by Red Hat.
The Default admin access group contains only users who have Organization Administrator permissions. This group is automatically maintained and users and roles in this group cannot be changed.
On the Hybrid Cloud Console navigate to Red Hat Hybrid Cloud Console > the Settings icon (⚙) > Identity & Access Management > User Access > Groups to see the current groups in your account. This view is limited to the Organization Administrator.
Predefined roles assigned to groups
The Default access group contains many of the predefined roles. Because all users in your organization are members of the Default access group, they inherit all permissions assigned to that group.
The Default admin access group includes many (but not all) predefined roles that provide update and delete permissions. The roles in this group usually include administrator in their name.
On the Hybrid Cloud Console navigate to Red Hat Hybrid Cloud Console > the Settings icon (⚙) > Identity & Access Management > User Access > Roles to see the current roles in your account. You can see how many groups each role is assigned to. This view is limited to the Organization Administrator.
1.1.2. Access permissions
The Prerequisites for each procedure list which predefined role provides the permissions you must have. As a user, you can navigate to Red Hat Hybrid Cloud Console > the Settings icon (⚙) > My User Access to view the roles and application permissions currently inherited by you.
If you try to access Red Hat Lightspeed features and see a message that you do not have permission to perform this action, you must obtain additional permissions. The Organization Administrator or the User Access administrator for your organization configures those permissions.
Use the Red Hat Hybrid Cloud Console Virtual Assistant to ask "Contact my Organization Administrator". The assistant sends an email to the Organization Administrator on your behalf.
Additional resources
For more information about user access and permissions, see User Access configuration guide for role-based access control (RBAC).
1.1.3. User Access roles for Red Hat Lightspeed tasks users
The following role enables enhanced access to remediations features in Red Hat Lightspeed:
Tasks administrator. The Tasks administrator role permits access to all Tasks capabilities to remotely run tasks on Red Hat Lightspeed-connected systems.
All members of the Default Admin Access group can also run Red Hat Lightspeed tasks.
A Tasks viewer role does not exist in Red Hat Lightspeed.
Chapter 2. Configuring notifications and integrations for Red Hat Lightspeed tasks events
You can configure the notifications service on the Red Hat Hybrid Cloud Console to send notifications whenever the Red Hat Lightspeed tasks service detects certain events that occur during the start and execution of a task. Use the notifications service as an alternative to continually checking the Activity tab for events related to the status of a task. The notifications service settings are available at Red Hat Hybrid Cloud Console > Settings > Notifications.
When configuring events for Red Hat Lightspeed tasks that you want notifications for, it is essential to understand the distinctions between a task, a task execution, and a task job. Also, be sure to know how they work together to perform a specific task in Red Hat Lightspeed.
- Red Hat Lightspeed tasks: a predefined script or playbook that helps you perform a specific task.
- Red Hat Lightspeed tasks execution: an instance of running that script or playbook on one or more systems.
- Red Hat Lightspeed tasks job: the execution of a specific task on a specific system.
For example, you can configure the notifications service to automatically send an email message when a Red Hat Lightspeed task starts, completes, or fails. As another example, you can configure the notifications service to automatically send an email message when a Red Hat Lightspeed task job starts or completes.
In addition to sending email messages, you can configure the notifications service to send event data in other ways:
- Using an authenticated client to query Red Hat Lightspeed APIs for event data
- Using webhooks to send events to third-party applications that accept inbound requests
- Integrating notifications with applications such as Splunk to route tasks events to the application dashboard, or to your preferred messaging application such as Slack or Microsoft Teams.
Configuring the notifications service to inform members of your Red Hat account of tasks events requires three main steps:
- An Organization Administrator creates a User Access group with the Notifications administrator role, and then adds account members to the group.
- A Notifications administrator sets up behavior groups for events in the notifications service. Behavior groups specify the delivery method for each notification. The Notifications administrator selects the event types to make available for the specified group of users. For example, a behavior group can specify whether to send email notifications to all users, or just to Organization Administrators.
- Members on the account who want to receive email notifications about events must set their user preferences so that they receive individual emails for each event.
To view configurable task events, you must be a Notifications administrator.
For more information about events and notifications, see the additional resources.
Chapter 3. Registering and connecting systems to Red Hat Lightspeed to run tasks
To work with Red Hat Lightspeed, you need to register your RHEL systems and enable system communication with Red Hat Lightspeed. In addition to communicating with Red Hat Lightspeed, you need to enable and install dependencies on Satellite version 6.11 or higher, Remote Host Configuration (rhc), rhc-worker-playbook and ansible, so that you can use task services, and other services in the Automation Toolkit.
For more information about enabling system communication with Red Hat Lightspeed and addressing dependencies, see:
Chapter 4. Running tasks in Red Hat Lightspeed
Red Hat Lightspeed provides built-in task playbooks that you can run on your remote Red Hat Enterprise Linux systems to automate common administrative actions. You can run tasks directly from the Red Hat Lightspeed UI.
The pre-built tasks that you can run in Red Hat Lightspeed include:
-
Run the Red Hat Lightspeed client (
insights-client) - Run the Ansible ping module
- Pre-conversion analysis for converting to RHEL
- Convert to RHEL from CentOS Linux 7
- Pre-upgrade analysis for in-place upgrade from RHEL 8
- Initiate update of image mode for RHEL host
- Initiate update of RHEL AI host
Note: Prerequisites and actions required to run specific Red Hat Lightspeed tasks will vary.
Use the following instructions to run a task in Red Hat Lightspeed:
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, andansible-core, as needed.- For more information, see Enabling host communication with Red Hat Lightspeed in the Red Hat Lightspeed Remediations Guide.
- You have addressed dependencies for Satellite version 6.11 or higher.
Procedure
- Navigate to Automation Toolkit > Tasks.
- Find a task in the list, and click Select systems. A table that lists the systems eligible to run the specified task is displayed.
- Optional: Edit the default task name to customize it with a more meaningful name so that you can find it on the Tasks Activity tab later.
After you run the task, you cannot change the task name again.
- Review the task-specific prerequisites shown in the brief description of the task, and take the required actions.
Select the checkbox beside the systems you want to run the task on. You can use filters to search and filter systems by:
- Name
- Operating system
- Tags
- Task eligibility
- Optional: For some tasks, you can configure how the task runs and is logged in Red Hat Lightspeed. If applicable, click Next and complete the task setup options. If not applicable, proceed to the next step.
- Click Run task. The task runs on the selected systems.
Results
A pop-up message is displayed and confirms the task’s success or failure. Click View progress to go to the task activity details page, where you can see how the task is progressing on each of your selected systems and alerts requiring attention.
A status of Completed indicates that the task ran successfully, but does not necessarily mean that the task achieved its intended goal.
Verification
Use the following steps to check the progress of the task and to verify that it ran successfully:
- Navigate to Automation Toolkit > Tasks > Activity to see the status of all the tasks you have run, including those in progress.
- Tasks are in chronological order, by the most recent run date and time. Use the search, filter, and sort features to find the task you just ran.
- Click the task to open the activity details.
Review the Status column to check whether there are any alerts or messages to resolve for your systems.
To see the full details of a message or alert, click the Show more caret beside the system name, as outlined in the following screen capture:
A Completed status indicates that the task ran successfully, but does not indicate that the task accomplished its intended goal.
Next Steps
Resolve any errors. For example, you might have an error that occurs because your systems are missing a software patch, update, or other package required by one or more actions in a task.
- After you resolve those errors, you can rerun the task from the task status details page within the Automation Toolkit > Tasks > Activity page. The task runs on the same systems as before, but you can also add more systems to the job.
Chapter 5. Using Red Hat Lightspeed tasks to help you convert from CentOS Linux 7 to RHEL 7
You can use Red Hat Lightspeed to help you convert from CentOS Linux 7 to RHEL 7.
For more information about using Red Hat Lightspeed tasks to help convert your systems, see Converting using Red Hat Lightspeed in the Converting from a Linux distribution to RHEL using the Convert2RHEL utility documentation.
Troubleshooting conversion-related RHEL tasks
Tasks help you update, manage, or secure your RHEL infrastructure by using Red Hat Lightspeed. Each task is a predefined playbook that executes a task from start to finish. For help with conversion-related tasks, see:
Chapter 6. Assessing system-upgrade readiness with the pre-upgrade analysis task
The pre-upgrade analysis task can run on any RHEL 8 system that is connected to Red Hat Lightspeed using the remote host configuration (rhc) solution. The task is a component of the in-place upgrade capability for Red Hat Enterprise Linux, also referred to as the Leapp tool.
For more information about the Leapp tool and using it to check upgrade readiness manually, see Upgrading from RHEL 8 to RHEL 9, Instructions for an in-place upgrade from Red Hat Enterprise Linux 8 to Red Hat Enterprise Linux 9.
You can verify that your system is connected to Red Hat Lightspeed by finding it in System > Inventory.
If not in the inventory, see Remote host configuration and management to learn how to connect systems to Red Hat Lightspeed.
The pre-upgrade analysis task checks the readiness of systems for upgrade from Red Hat Enterprise Linux (RHEL) 8 to RHEL 9. If Red Hat Lightspeed detects upgrade-blocking issues, you can see more information about the issues, including steps to resolve them.
You can also run the Leapp utility manually on systems. When a Red Hat Lightspeed-connected system has a Leapp report in its archive, you can see results from the report in Red Hat Lightspeed, regardless of whether the utility ran manually or as a task that ran from within Red Hat Lightspeed.
The steps in this procedure assume that you have read and understood the following information before you attempt to do any upgrade-related actions by using Red Hat Lightspeed:
Prerequisites
Before you run the pre-upgrade analysis task, ensure the following prerequisites are met:
- Your systems are eligible for an in-place upgrade. For more information, see the in-place upgrade documentation for system requirements and limitations.
Your RHEL systems are connected to Red Hat Lightspeed by using the remote host configuration solution to run tasks and remediation plans from within the Red Hat Lightspeed UI.
- For more information, see Remote host configuration and management.
- You are logged in to the Red Hat Hybrid Cloud Console as a user with the Tasks administrator role assigned.
All members of the Default admin access group have Tasks administrator access. If you are not a member of a User Access group with this role, you will not be permitted to see tasks on the Tasks page. For more information about User Access, including how to request more access to Red Hat Lightspeed features, see User Access configuration guide for role-based access control (RBAC)].
6.1. Running the pre-upgrade analysis task
Red Hat Lightspeed provides built-in task playbooks to help you prepare your Red Hat Enterprise Linux systems for upgrades. Tasks are available to analyze selected Red Hat Enterprise Linux systems in your organization and identify required actions that must be completed before you start to upgrade those systems.
Use the following procedure to run the pre-upgrade analysis task to check the readiness of your systems for upgrading from RHEL version 8 to 9.
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.
Procedure
- Navigate to Automation Toolkit > Tasks.
- In the list of available tasks presented, find the task titled Pre-upgrade analysis for in-place upgrade from RHEL 8, and click the name to open the details.
Review the task-specific prerequisites shown in the brief description of the task, and take the required actions to ensure they are met.
TipYou can view further details of the pre-upgrade analysis utility task by clicking Download preview of playbook.
- Eligible systems are listed on the task details page. Select the systems you want to run the task on.
- Click Run task. The task runs on the selected systems.
Result
A pop-up message confirms the task’s success or failure. Click View progress to go to the task activity details page, where you can see how the task is progressing on each of your selected systems and alerts requiring attention.
A status of Completed indicates that the task ran successfully, but does not necessarily mean that the task achieved its intended goal.
Verification
Use the following steps to check the progress of the task and to verify that it ran successfully:
- If you missed the pop-up message with the View progress link, navigate to Automation Toolkit > Tasks > Activity to see the status of all the tasks you have run, including those in progress.
- Tasks are in chronological order, ordered by the most recent run date and time. Use the search, filter, and sort features to find the task you just ran.
- Click the task to open the activity details.
Review the Status column to check whether there are any alerts or messages to resolve for your systems.
- To see the full details of a message or alert, click the Show more caret icon beside the system name, as outlined in the following screen capture:
6.2. Reviewing the pre-upgrade analysis task report
After running the pre-upgrade analysis task on your systems, review the detailed results and take the required actions that Red Hat Lightspeed recommends.
Prerequisites
- You are logged in to the Red Hat Hybrid Cloud Console.
- You are a member of a User Access group that has the Tasks administrator role.
Procedure
- Navigate to Automation Toolkit > Tasks > Activity to see the status of all the tasks you have run, including those in progress.
- Tasks are in chronological order, by the most recent run date and time. Use the search, filter, and sort features to find the pre-upgrade analysis task you just ran.
- Click the task name to open the activity details.
Review the Status column to check whether there are any alerts or messages to resolve for your systems.
- Alerts are indicated in the table by the red High risk tag.
- Warnings are indicated in the table by the orange-coloured Low risk tag.
Informational messages are indicated in the table by the blue-coloured Info tag.
ImportantSome alerts are classified as official inhibitors, and you cannot proceed with the upgrade until these are remediated. Some items in the table are lower in severity and are informative messages that do not require remediation for the upgrade to proceed.
Expand the full details of a message or alert by clicking the Show more caret icon beside the system name, as outlined in the following screen capture:
- If the activity report has high-risk upgrade-inhibiting alerts, take the required actions to resolve them on your systems, and then re-run the pre-upgrade task to assess the impact of your remediation efforts.
- Review the rest of the report thoroughly and take the required actions.
6.3. Viewing upgrade-inhibiting recommendations
After running the pre-upgrade analysis task or manually running the Leapp tool on individual systems, you can view a list of recommendations for upgrade-inhibiting issues in your RHEL infrastructure.
For pre-upgrade recommendations, Red Hat Lightspeed provides the following information:
- Recommendation details
- Affected-system information
- Total risk and impact insights
- Risk to system availability during resolution actions
Prerequisites
You are logged in to the Red Hat Hybrid Cloud Console.
By default, all Red Hat Lightspeed users can view the list of in-place upgrade recommendations.
Procedure
Go to Red Hat Lightspeed > Operations > Advisor > Topics > In-place upgrade to view recommendations affecting the success of in-place upgrades.
NoteThe in-place upgrade recommendations list only shows recommendations that Red Hat Lightspeed has identified as upgrade inhibitors. You can see all in-place upgrade recommendations, including non-inhibitors, in the detailed view of each executed task.
6.4. Remediating upgrade-inhibiting recommendations
You can use the in-place upgrade recommendations list as a basis for remediating upgrade-inhibiting issues on systems in your infrastructure.
Some recommendations have a playbook available for automating the execution of remediations directly from the Red Hat Lightspeed UI. However, some recommendations require manual resolutions, the steps of which are customized for the system and recommendation pair, and are provided with the recommendation. You can tell which recommendations have playbooks available by viewing the Remediation type column in the recommendations table.
To find the recommendations that have playbooks available to execute, use the filter and sort options at the top of the table to narrow down the list.
- Filter: Use the search bar or select a specific item from the dropdown menu.
- Sort: Click the Remediation type column header to sort the recommendations by Manual or Playbook types.
For more information about Red Hat Lightspeed remediations, see the Red Hat Lightspeed Remediations Guide.
6.4.1. Remediating RHEL upgrade-inhibiting recommendations with a remediation plan
Automate the remediation of upgrade-inhibiting recommendations by creating a remediation plan in Red Hat Lightspeed. Red Hat Lightspeed generates an Ansible Playbook to execute the necessary actions on selected systems.
Use the following procedure to locate inhibitor issues and select recommendations and systems for remediation.
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.
Procedure
- Navigate to Operations > Advisor > Topics > In-place upgrade. A table lists the recommended remediations affecting in-place upgrades.
Narrow the recommendations list using the table’s filter and sort options:
- Filter: Use the search bar or select an item from the dropdown menu.
- Sort: Click column headers, for example, Name, Remediation type, Systems, or Total risk.
Choose a recommendation with a Remediation type of Playbook.
NoteRecommendations with playbooks are identified by the Remediation type column.
For each recommendation with an available playbook:
- Click the recommendation to view details and affected systems.
- Check the box next to each system you want to add to the playbook, and then click Plan remediation.
- In the pop-up, select Create a new playbook and enter a name, then click Next.
- Optional: Alternatively, select the option to add the resolution for the selected systems to an existing playbook in your organization.
- Review the included systems and click Next.
Review the included recommendation. You can click the caret next to the recommendation name to see included systems.
ImportantIf the issue or risk requires a reboot, all systems in the remediation plan will automatically reboot. To manually reboot after plan execution, toggle the Auto-reboot button.
- Click Submit. The final pop-up view confirms that the playbook was created successfully. You can select to return to the application or open the playbook.
- Find and open the playbook in Automation Toolkit > Remediation Plans.
- The playbook includes a list of actions. Select the actions to execute by checking the box next to each one.
- Click Execute playbook to run the playbook on the specified systems.
- When prompted, click Execute playbook on systems. The playbook runs on those systems.
6.4.2. Remediating RHEL upgrade-inhibiting recommendations manually
Some issues cannot be addressed by creating and executing a remediation plan in Red Hat Lightspeed. Instead, they require manual actions or intervention. For example, you can remediate upgrade-inhibiting recommendations by manually applying resolution steps on affected systems.
The following procedure outlines how to determine the resolution steps for a system that Red Hat Lightspeed recommends you manually remediate.
Prerequisites
- You are logged into the Red Hat Hybrid Cloud Console.
Procedure
- Navigate to Operations > Advisor > Topics > In-place upgrade to view recommendations affecting the success of in-place upgrades.
- Use the search and filtering function in the table to sort the items by Remediation type.
- Choose a recommendation with the word "Manual" in the Remediation type column, which indicates that the issue requires manual remediation.
- Click the recommendation name. The full details of the recommendation are displayed, along with a list of impacted systems on the lower part of the page.
For each impacted system:
- Expand the caret icon to view the steps to resolve the recommendation.
- Complete the recommended actions directly on the system.
Chapter 7. Using Red Hat Lightspeed tasks to update image mode RHEL systems
When building systems by using image mode for RHEL, you can connect your systems to Red Hat Lightspeed. Once connected, use the Red Hat Lightspeed tasks, Initiate an update of your image mode RHEL host, to update your Red Hat Lightspeed-connected systems to the latest versions of RHEL. Red Hat Enterprise Linux version 9.4 and later includes image mode for RHEL.
Image mode for RHEL uses the terms update and upgrade interchangeably.
7.1. Running Red Hat Lightspeed tasks to update image mode for RHEL systems
Red Hat Lightspeed also provides pre-built tasks to help you keep your image mode for Red Hat Enterprise Linux systems updated. From within the Red Hat Lightspeed UI, you can run a task to initiate an update to your image mode for RHEL systems, otherwise known as bootc images.
If you have a large number of image mode for Red Hat Enterprise Linux systems to update, run the Red Hat Lightspeed task titled "Initiate update of image mode for RHEL host" to automate the following actions:
- Checks the container repository for a new container image
- Downloads the image and extracts content for use on the next boot
- Reboots the host to pull in new image content if updated content is available
- Provides progress results about the image update
You might also want to use this Red Hat Lightspeed task when you want to avoid using the automatic upgrade option for your image mode for Red Hat Enterprise Linux systems.
Image mode for Red Hat Enterprise Linux is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using Technical Preview features in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
- Completing the next step results in a reboot of the selected systems.
- If you need to roll back your systems to an earlier state, see Managing RHEL bootable images Red Hat Enterprise Linux 9 in Using image mode for RHEL to build, deploy, and manage operating systems.
Prerequisites
- You are logged in to the Red Hat Hybrid Cloud Console.
- You are a member of a User Access group that has the Tasks administrator role.
You have systems that are registered and connected to Red Hat Lightspeed by using one of the following methods:
-
The remote host configuration (rhc)
rhc-worker-playbookandansible-coretools. Satellite 6.11 or higher.
- For more information, see Enabling host communication with Red Hat Lightspeed in the Red Hat Lightspeed Remediations Guide.
-
The remote host configuration (rhc)
The target systems were built with Red Hat Enterprise Linux
bootcimages by using thebootcimage builder.For more information about how you can use Red Hat Enterprise Linux
bootcimages to build, deploy, and manage an operating system as if it were any other container, see the following documentation:
Procedure
- Navigate to Automation Toolkit > Tasks. The Available tab opens with a list of tasks available for you to run.
- Find the task Initiate update of image mode for RHEL host, and click Select systems. The systems on which you can run the task are displayed in a table.
Select the checkbox beside the systems you want to run the task on. By default, the table is filtered by
bootcsystems registered by using RHC. You can use filters to search and filter systems by:- Name
- Operating system
- Tags
- Task eligibility
- Click Run Task. A pop-up alerts you that the task is running.
- Review the information in the Status and Message fields on the Activity page.
Expand the caret beside the system name to view more details about the task, for example, the operating system version and the image hash.
NoteSometimes, when you run a task, Red Hat Lightspeed might report that there are zero updates because the system is already up to date.
Troubleshooting
- To view the detailed progress and history of all tasks in your Red Hat Lightspeed organization, navigate to Automation Toolkit > Tasks > Activity. From here, you can see whether any tasks failed and get more information to help you understand why.
- To resolve issues with the task, you can find the answers to some common issues in the linked documentation for other tasks. Red Hat Lightspeed tasks use a common framework of tools, language, and resources within the service.
- If you have trouble completing a task, open the activity results page for the last time the task ran, and then try rerunning the same task by clicking Run task again.
- For more information about how to resolve issues with similar error messages, review Troubleshooting issues with Red Hat Lightspeed conversions.
Providing feedback on Red Hat documentation
We appreciate and prioritize your feedback regarding our documentation. Provide as much detail as possible, so that your request can be quickly addressed.
Prerequisites
- You are logged in to the Red Hat Customer Portal.
Procedure
To provide feedback, perform the following steps:
- Click the following link: Create Issue
- Describe the issue or enhancement in the Summary text box.
- Provide details about the issue or requested enhancement in the Description text box.
- Type your name in the Reporter text box.
- Click the Create button.
This action creates a documentation ticket and routes it to the appropriate documentation team. Thank you for taking the time to provide feedback.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}