Logrotate configs must be adjusted for containerized services logs
Bug #1700912 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
Logs collection part is addressed in the spec https:/
Logrotate configs covering added log paths for containers must come from either openstack packages, or a tripleo package.
Changed in tripleo: | |
milestone: | none → pike-3 |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: containers |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
To post a comment you must log in.
Perhaps the logrotate scripts could come with the openstack- tripleo- common- containers( -base?? ?) package, but sending SIGHUP to containerized openstack (and not only) services will be a tricky thing . Restarting containers could work as well, but looks too intrusive.