Description of problem:
When deploying with SSL you see this warning in the beginning of the deployment:
WARNING: Following parameters are defined but not used in plan. Could be possible that parameter is valid but currently not used.
The deploy command I used:
openstack overcloud deploy --templates --ntp-server clock.redhat.com -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/enable-tls.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-ip.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/inject-trust-anchor.yaml -e custom.yaml
Doing "openstack stack environment show overcloud" shows that the appropriate override is in the resource registry:
which should use the parameters. Downloading "https://192.168.24.2:13808/v1/AUTH_d89c3add038047b0b4bedc6bebe43c87/overcloud/puppet/extraconfig/tls/tls-cert-inject.yaml" from swift shows the correct file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy an overcloud with SSL like in the above description
A warning appears in the beginning of the deployment
I'm actually not sure how to address this nor what's going on. The parameters should be in the plan, as they're passed as part of the environment files, and as part of those environment files is also de registry override that defines the resource that takes them into use.
We're going to do some filtering on these vars to reduce the ones that get printed out because they are generated by us (e.g. Docker*Image vars). This is mostly here for the end user to reference if they end up having issues with with some setting being applied. I've posted an upstream bug around this where the status can be tracked and proposed a patch to update the text a bit more to indicate this situation.