Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1853333

Summary: [OSP13->OSP16.1] FFU commands from the 10 to 13 upgrade are still available in the 13 to 16.1
Product: Red Hat OpenStack Reporter: Jose Luis Franco <jfrancoa>
Component: python-tripleoclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: David Rosenfeld <drosenfe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16.1 (Train)CC: aschultz, hbrock, jslagle, mburns
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-02 14:15:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jose Luis Franco 2020-07-02 12:21:59 UTC
Description of problem:

The OSP13 to OSP16.1 FFU upgrade workflow relies on the "openstack overcloud upgrade" commands instead of the old "openstack overcloud ffwd-upgrade" ones. However, these ffwd-upgrade commands are still available, which could cause confusion among customers.

This bug is intended to track all the old FFWD bits removal which aren't needed anymore.


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


How reproducible:

(undercloud) [stack@undercloud-0 ~]$ openstack overcloud --help | grep ffw
  overcloud ffwd-upgrade converge
  overcloud ffwd-upgrade prepare
  overcloud ffwd-upgrade run


Steps to Reproduce:
1.
2.
3.

Actual results:

openstack overcloud ffwd-upgrade <> commands are available

Expected results:

openstack overcloud ffwd-upgrade <> commands aren't available

Additional info:

Comment 1 Jose Luis Franco 2020-07-02 14:15:39 UTC
I got a BZ timeout when creating this BZ and didn't get awareness that it really got created, so I recreated it again in https://bugzilla.redhat.com/show_bug.cgi?id=1853334

Closign as duplicate.

*** This bug has been marked as a duplicate of bug 1853334 ***