Fluentd custom file not idempotent when overwriting default file
Bug #1840166 reported by
Scott Solkhon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Scott Solkhon | ||
Train |
Fix Released
|
Medium
|
Scott Solkhon |
Bug Description
If we have a custom fluentd input/output/filter config with the same name as a
default config, we will first write out the default config then replace it with
the custom one, resulting in two changed tasks. This change fixes this by
skipping default configs that have been customised.
Changed in kolla-ansible: | |
status: | New → In Progress |
assignee: | nobody → Scott Solkhon (scott.solkhon) |
Changed in kolla-ansible: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/676216 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=dcaa5f0b3d9 953a562c55363b4 09bf5cb289f2bd
Committed: https:/
Submitter: Zuul
Branch: master
commit dcaa5f0b3d9953a 562c55363b409bf 5cb289f2bd
Author: Scott Solkhon <email address hidden>
Date: Tue Aug 13 15:22:37 2019 +0000
Fix idempotency of fluentd customisations
Fix fluentd config from overwriting custom config with the same filename
Closes-Bug: #1840166 15f590901b21209 50d602f847f
Change-Id: I42c54463810330