Browse Source

Disable LoggingConfiguration by default

This patch makes it possible to avoid issues with LoggingConfiguration
parameters during stack update.

Closes-Bug: #1881871
Change-Id: Ie8207cd3ca40d687b374d2f9ee3129f27245d290
changes/74/733074/1
Martin Magr 1 year ago
parent
commit
576c067f07
  1. 2
      environments/logging-environment.yaml
  2. 2
      overcloud-resource-registry-puppet.j2.yaml

2
environments/logging-environment.yaml

@ -5,6 +5,7 @@
resource_registry:
OS::TripleO::Services::Fluentd: ../deployment/deprecated/logging/fluentd-container-puppet.yaml
OS::TripleO::LoggingConfiguration: ../deployment/deprecated/logging/fluentd-config.yaml
#parameter_defaults:
@ -28,4 +29,3 @@ resource_registry:
# -----BEGIN CERTIFICATE-----
# ...certificate data here...
# -----END CERTIFICATE-----

2
overcloud-resource-registry-puppet.j2.yaml

@ -250,7 +250,7 @@ resource_registry:
OS::TripleO::Services::TripleoValidations: OS::Heat::None
OS::TripleO::Services::UndercloudUpgrade: OS::Heat::None
OS::TripleO::Services::Collectd: OS::Heat::None
OS::TripleO::LoggingConfiguration: deployment/deprecated/logging/fluentd-config.yaml
OS::TripleO::LoggingConfiguration: OS::Heat::None
OS::TripleO::Services::ManilaApi: OS::Heat::None
OS::TripleO::Services::ManilaScheduler: OS::Heat::None
OS::TripleO::Services::ManilaShare: OS::Heat::None

Loading…
Cancel
Save