Bug 1900663 - DCN - FFU 16.2 to 17.1.1 computes only
Summary: DCN - FFU 16.2 to 17.1.1 computes only
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: z3
: 17.1
Assignee: Ollie Walsh
QA Contact: Marian Krcmarik
URL:
Whiteboard:
Depends On: 2016660
Blocks: 1997638 2222683
TreeView+ depends on / blocked
 
Reported: 2020-11-23 13:49 UTC by Gregory Charot
Modified: 2024-05-03 13:40 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this update, Red Hat support for Framework for upgrades is expanded to include DCN deployments without storage at the edge.
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2744 0 None None None 2022-04-26 14:19:00 UTC
Red Hat Issue Tracker RHOSPDOC-1554 0 None None None 2024-03-18 13:13:53 UTC

Description Gregory Charot 2020-11-23 13:49:34 UTC
Description of problem:

Perform a Fast Forward Upgrade from OSP 16.x to OSP 17 when deploying OSP DCN with edge sites composed of compute nodes only

Version-Release number of selected component (if applicable):

17

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 spower 2022-05-11 10:23:38 UTC
This RFE is not marked as an MVP for 17.0, so it is being moved for consideration to OSP 17.1. As stated in the OSP Program Call, QE and Docs only have the capacity to verify and document MVP features for OSP 17.0.

Comment 8 Marian Krcmarik 2023-10-13 19:58:09 UTC
I've managed to perform FFU (OSP+System upgrade) of DCN env:
Central site (3 cont + 2 computes), 2 DCN sites with 2 computes without storage on the edge.

The FFU finished successfully and tempest tests seem to be passing (even with combination with MultiRHEL).


Note You need to log in before you can comment on or make changes to this bug.