Description of problem:
VNX tripleo support is backported upstream. can we backport it to OSP12?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
All of the VNX support will be included in 12z2.
According to our records, this should be resolved by openstack-tripleo-heat-templates-7.0.9-8.el7ost. This build is available now.
According to our records, this should be resolved by puppet-tripleo-7.4.8-5.el7ost. This build is available now.
According to our records, this should be resolved by puppet-cinder-11.5.0-3.el7ost. This build is available now.
The version of OSP12 on FutureVille2 didn't have the backports. Assuming the Customer that is waiting for testing this on OSp12 might not have it and will need a hotfix that will include these. Else we have to make them get it from upstream and use some custom options in the deployment of overcloud which can get messy
My apolgies, I was mistaken. Apparently the upstream patches on stable/pike
just barely missed (by a couple of days) the upstream RDO import that formed
the basis for OSP-12z2. There are subsequent RDO packages that contain the VNX
backport, and confirmed those packages will be included in z3.
I am not sure what it will take to provide hotfixes. The tripleo-heat-templates
piec is easy, but the puppet-tripleo package will need to be rolled into the
contents of openstack-puppet-modules, and then have that built into
ack the hotfix for when builds are ready
Created attachment 1420717 [details]
Created attachment 1420718 [details]
we have attached puppet-tripleo-7.4.8-6.el7ost.noarch.rpm and openstack-tripleo-heat-templates-7.0.9-9.el7ost.noarch.rpm could you please validate the functionality.
The futureville3 stamp is currently being used for baremetal certification. This may take some time
May be you can do verification solely based on checking code in the RPM
We really should be verifying based on actual deployments being successful. That's the value that DCI is supposed to bring. It also avoids a few unfortunate mistakes where we "verified" a TripleO patch for other Cinder backends that actually didn't work as intended.
I have asked the baremetal certification engineer about the availability of the Stamp for verification. Will keep posted
This will probably be the next puddle, we don't have access to puddle yet. What goneri helped me installed today was one version behind
Its one version behind
This can be QA'd using the following packages or later:
We are already installing OSP13 on Futureville3 and the customer is asking us to focus on OSp13 testing, so I'm not sure if we should spend any cycles testing this.
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.