Old container configs aren't removed from container-startup-config directory

Bug #1884577 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Emilien Macchi

Bug Description

There is no mechanism in place that will clean up old configs in /var/lib/tripleo-config/container-startup-config.
So when running FFU from Queens to Train (and disabling Paunch in Train), some leftover configs will remain in var/lib/tripleo-config/container-startup-config that can cause issue when running minor updates after the FFU proceeded.

tags: added: train-backport-potential
tags: added: ussuri-backport-potential
tags: added: upgrade
tags: added: idempotency
Revision history for this message
Emilien Macchi (emilienm) wrote :
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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