Provide customers more stable, flexible, reliable and faster storage service deployments with more reliable and flexible lifecycle management and possibility to rollback when something goes wrong.
Changing to ON_DEV - work already in progress.
The Manila share image is apparently not getting built for OSP12 yet. We added the image after the M2 upstream TripleO milestone here:
Could we get another ack on this so that downstream can start building this image.
Also, please CC jschluet so that he knows about the exception has been granted.
We were able to successfully complete a full regression run against the NetApp cDOT Manila Driver when deployed in a containerized manner. Marking as verified.
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.