-
Bug
-
Resolution: Unresolved
-
Normal
-
ACM 2.10.0
-
False
-
None
-
False
-
No
-
-
-
Important
-
Customer Facing
Create an informative issue (See each section, incomplete templates/issues won't be triaged)
Using the current documentation as a model, please complete the issue template.
Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.
Prerequisite: Start with what we have
Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:
- Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes
- Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs
Describe the changes in the doc and link to your dev story
Provide info for the following steps:
1. - [ X ] Mandatory Add the required version to the Fix version/s field.
2. - [ X ] Mandatory Choose the type of documentation change.
- [ ] New topic in an existing section or new section
- [ X ] Update to an existing topic
3. - [ ] Mandatory for GA content:
- [ ] Add steps and/or other important conceptual information here:
- [ ] Add Required access level for the user to complete the task here:
- [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
- [ ] Add link to dev story here:
4. - [ X ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:
The link to documentation:
The ACM upgrade is supported only to just next Y-release: you can upgrade to 2.Y only from 2.Y-1. This is mentioned in step 7, but this is only a small, not-highlighted sentence.
Select the channel for the next available feature release, but do not attempt to skip a channel.
The importance of this message is very high to be hidden in the middle of other text and we have cases caused by missing this info. This is a big problem.
I would recommend to highlight this message preferably with a big red box and at the top of the Upgrade chapter:
IMPORTANT: Upgrades are only supported from the immediately preceding version. For example, you can upgrade to version 2.10 only from version 2.9
Thank you...