Red Hat Bugzilla – Bug 1295407
Deployment fails: ERROR: The Parameter (CinderRbdPoolName) was not defined in template.
Last modified: 2016-04-07 17:44:25 EDT
Description of problem:
I am trying to do a RHOS8 deployment and passing the Ceph pool names into an environment files. Deployment fails because there is no CinderRbdPoolName defined in the template.
This used to work with RHOS7.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to deploy overcloud
openstack overcloud deploy \
--templates ~/templates/my-overcloud \
-e ~/templates/virt-ha-ceph.yaml \
-e ~/templates/my-overcloud/environments/network-isolation.yaml \
-e ~/templates/network-environment.yaml \
-e ~/templates/firstboot-environment.yaml \
-e ~/templates/ceph.yaml \
2. Contents of ~/templates/ceph.yaml:
stack@instack:~>>> cat ~/templates/ceph.yaml
# the following parameters enable Ceph backends for Cinder, Glance, and Nova
# finally we disable the Cinder LVM backend
stack@instack:~>>> time bash deploy.command
Deploying templates in the directory /home/stack/templates/my-overcloud
ERROR: The Parameter (CinderRbdPoolName) was not defined in template.
Same applies to Nova and Glance, i.e.:
ERROR: The Parameter (NovaRbdPoolName) was not defined in template.
ERROR: The Parameter (GlanceRbdPoolName) was not defined in template.
in RHOS8 these should be passed via
unfortunately the sample storage-environment.yaml file in RHOS7 used to have "parameters:" but the first will work with RHOS7 too.
Both the sample environment files puppet-ceph-external.yaml and storage-environment.yaml in RHOS8 use "parameter_defaults:" now.
Can you please confirm that this fixes the problem?
Yogev I think you tested this as well recently and were able to customize the pool names?
verification passed in openstack-tripleo-heat-templates-0.8.8-2.el7ost.noarch
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.