rsyslog-client configuration is incomplete after first playbook run
Bug #1458822 reported by
Jesse Pretorius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Jesse Pretorius | ||
Kilo |
Fix Released
|
High
|
Jesse Pretorius | ||
Trunk |
Fix Released
|
High
|
Jesse Pretorius |
Bug Description
After the first run through of the playbooks is done, the rsyslog client configuration is incomplete. In many cases the log files aren't configured because they don't yet exist at the time the playbook tries to find them.
We should either explicitly define a list of log files or we should implement a re-run of the rsyslog client configuration later on.
summary: |
- run-playbooks does not do rsyslog-client configuration + rsyslog-client configuration is incomplete after first playbook run |
description: | updated |
Changed in openstack-ansible: | |
assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
importance: | Undecided → High |
milestone: | none → 11.0.2 |
status: | New → Confirmed |
To post a comment you must log in.
The notification to restart the nova services happens after the rsyslog configuration. We need to flush the handlers before going ahead with the rsyslog configuration.