Description of problem: This is a placeholder for defining the minimal candidate workflow for Fast Forward Upgrades (10-13). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We are aiming to have following Minimal Viable product (aka MVP) test as follow: 3 controller (HA) + 2/3 computes (to allow migration) + 3 internal ceph -> infrastructure networking: ipv4, tenant networking: vxlan, stack name: default. This a basic set of features we have in RHOS and majority of our customer have such deployment.
I think we are testing MVP presently with a number of patches that are being tracked individually. I would suggest we either move this to ON_QA or keep this here as a tracker but make sure all the depends on References the correct set of bugs we are actively working on.
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/RHEA-2018:2086