Container-puppet (former docker-puppet) tool does not synchronize removed config files

Bug #1836155 reported by Bogdan Dobrelya
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Bogdan Dobrelya

Bug Description

T-h-t common/container-puppet.py tool only propagates config files removed by puppet to /var/lib/config-data/${NAME} (where NAME is the config-volume name of a service). But those do not end up being removed in the /var/lib/config-data/puppet-generated/${NAME} immediately. While it must be.

This creates situations, when potentially conflicting configurations, like loaded Apache MPM modules, may co-exist. Kolla extended start picks it up later and might fail, when it bootstraps the main service $NAME container.

Changed in tripleo:
importance: Undecided → High
milestone: none → train-2
tags: added: containers idempotency
Changed in tripleo:
status: New → In Progress
assignee: nobody → Bogdan Dobrelya (bogdando)
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
importance: High → Medium
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.