This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2290578 - Note in the documentation provides no background of known issue
Summary: Note in the documentation provides no background of known issue
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z5
: 17.1
Assignee: kgilliga
QA Contact: Archana Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-05 15:54 UTC by Eric Nothen
Modified: 2025-01-15 20:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-01-15 20:43:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   OSP-32212 0 None None None 2025-01-15 20:43:54 UTC
Red Hat Issue Tracker OSP-32213 0 None None None 2024-06-05 15:58:11 UTC

Description Eric Nothen 2024-06-05 15:54:19 UTC 
Description of problem:

FFU 16.2 - 17.1 document, section 5.1 [0], procedure step #3 says:

~~~
Verify that the following files that were exported during the undercloud upgrade contain the expected configuration for the overcloud upgrade...
~~~
and there's a note that reads:
~~~
If the files were not generated after the undercloud upgrade, contact Red Hat Support.
~~~

Red Hat support has no information about the background of this known issue and has no idea what to do with it. BZ or Jira should be referenced in the note, so that we can create a KCS article with further troubleshooting instructions o a workaround procedure.


[0] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/framework_for_upgrades_16.2_to_17.1/index#running-the-overcloud-upgrade-preparation_overcloud-adoption
Note You need to log in before you can comment on or make changes to this bug.