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

Bug 1598203

Summary: FFU: remove the under development warning once full testing is complete
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: python-tripleoclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: ccamacho, dbecker, dsorrent, hbrock, jfrancoa, jslagle, mbracho, mbultel, mburns, morazi, rhos-maint, yprokule
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-9.2.3-6.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-13 22:27:09 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 Marius Cornea 2018-07-04 16:03:18 UTC 
Description of problem:
Currently any ffwd cli invocations show the following warning:

Warning! The TripleO Fast Forward Upgrade workflow is currently considered under development. In particular invocations of the ffwd-upgrade cli should be initially limited to development/test environments. Once and if you decide to use ffwd-upgrade in production, ensure you are adequately prepared with valid backup of your current deployment state.

We should remove this warning once full testing is complete.
Comment 1 mathieu bultel 2018-07-09 12:52:15 UTC 
Hi Maria,

Can you confirm when we should remove this warning ?
Comment 5 Carlos Camacho 2018-09-10 12:39:17 UTC 
The cherrypick is to be merged soon
Comment 13 Yurii Prokulevych 2018-11-09 07:01:50 UTC 
Verified with python-tripleoclient-9.2.6-2.el7ost.noarch
Comment 15 errata-xmlrpc 2018-11-13 22:27:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3587
Comment 16 Red Hat Bugzilla 2023-09-14 04:30:57 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days