Fix absolute paths in scenario001-multinode.yaml
All paths should be relative as we should not rely on the package location - this can easily be overridden via --templates, and this is exactly what we do for the upgrades job, where this will break because we'll include the wrong (newer) version of these services when deploying the older pre-upgrade overcloud. Change-Id: Id8aea09305c0857253c44477945e34377cca64ca
This commit is contained in:
parent
e8dc8c6fae
commit
22433c54af
@ -19,8 +19,8 @@ resource_registry:
|
||||
OS::TripleO::Tasks::ControllerPreConfig: ../../extraconfig/tasks/pre_puppet_pacemaker.yaml
|
||||
OS::TripleO::Tasks::ControllerPostConfig: ../../extraconfig/tasks/post_puppet_pacemaker.yaml
|
||||
OS::TripleO::Tasks::ControllerPostPuppetRestart: ../../extraconfig/tasks/post_puppet_pacemaker_restart.yaml
|
||||
OS::TripleO::Services::FluentdClient: /usr/share/openstack-tripleo-heat-templates/puppet/services/logging/fluentd-client.yaml
|
||||
OS::TripleO::Services::SensuClient: /usr/share/openstack-tripleo-heat-templates/puppet/services/monitoring/sensu-client.yaml
|
||||
OS::TripleO::Services::FluentdClient: ../../puppet/services/logging/fluentd-client.yaml
|
||||
OS::TripleO::Services::SensuClient: ../../puppet/services/monitoring/sensu-client.yaml
|
||||
|
||||
parameter_defaults:
|
||||
ControllerServices:
|
||||
|
Loading…
x
Reference in New Issue
Block a user