rsyslog-client configuration is incomplete after first playbook run

Bug #1458822 reported by Jesse Pretorius
6
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
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

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.

Changed in openstack-ansible:
assignee: nobody → Jesse Pretorius (jesse-pretorius)
importance: Undecided → High
milestone: none → 11.0.2
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/185662

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/185662
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=c7951c43e2f3bae01c595151af33d35dcf0b3ca4
Submitter: Jenkins
Branch: master

commit c7951c43e2f3bae01c595151af33d35dcf0b3ca4
Author: Jesse Pretorius <email address hidden>
Date: Tue May 26 17:43:50 2015 +0100

    Add handler flushing to roles that need it

    This patch adds handler flushing as the last task in each role to ensure
    that there are log files present when the rsyslog client configuration
    task is executed a little later in the playbook that consumes the role.

    Closes-Bug: #1458822
    Change-Id: I92a26b620aa7bc0fbe33175594d37da7d5aca7df

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/185901

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/185901
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=8e1f21a6a225a6037d0e24d3022a293132514a30
Submitter: Jenkins
Branch: kilo

commit 8e1f21a6a225a6037d0e24d3022a293132514a30
Author: Jesse Pretorius <email address hidden>
Date: Tue May 26 17:43:50 2015 +0100

    Add handler flushing to roles that need it

    This patch adds handler flushing as the last task in each role to ensure
    that there are log files present when the rsyslog client configuration
    task is executed a little later in the playbook that consumes the role.

    Closes-Bug: #1458822
    Change-Id: I92a26b620aa7bc0fbe33175594d37da7d5aca7df
    (cherry picked from commit c7951c43e2f3bae01c595151af33d35dcf0b3ca4)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

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.