-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Transfer upgrade/update known issues to rel notes
-
False
-
-
False
-
Not Selected
-
?
-
?
-
To Do
-
?
-
rhos-ops-day1day2-upgrades
-
?
-
100% To Do, 0% In Progress, 0% Done
-
-
-
-
Low
In the Update guide there is a set of known issues: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/updating_your_environment_to_the_latest_maintenance_release/index#known-issues-updates_preparing-minor-update
In the release notes there is another set of known issues: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/release_notes/index#control-plane-known-issues
It is unclear why these are separated, and whether they are synchronised or filtered in some way.
It seems like it would be better to establish a single place for known issues and to ensure that the update guide refers to the same location/content. This will ensure that customers are sufficiently informed and reduces the maintenance of the documentation.
It may be worth having some sort of guide for how the release note known issues should be used when it comes to the known issues. For example, a question that may arise if whether a known issue from 18.0.2 still relevant when updating to 18.0.5?
- relates to
-
OSPRH-18540 In the RHOSO18 Known Issue section of the update documentation we shouldn't point to FR2
-
- Closed
-