Description of problem: Requesting [RHOSP16.1][Backport][Cinder] Rebranding of VxFlex OS driver to PowerFlex Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Is this landing in z2? Do not see it moved to modified state yet?
(In reply to arkady kanevsky from comment #1) > Is this landing in z2? Do not see it moved to modified state yet? Expected to be z3.
Pablo, can we land it in z2?
We really need it for z2. Part of promise to several major telco customers and certification needs it.
Clearing the needinfos on me, all the powerflex re-brand Bzs are targeted to z3, while the core fixes needed to cert powerflex are in z2. If there's any further questions, please look to John Visser to check things. Thanks, Paul
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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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-2020:5413