One notify in tacker is not correct

Bug #1700007 reported by zhongshengping
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
zhongshengping
Ocata
New
Undecided
Unassigned
Pike
Fix Released
Medium
zhongshengping

Bug Description

There is a notify "Restart tacker containers" in `roles/tacker/tasks/config.yml`:

```

- name: Copying over existing policy.json
  template:
    src: "{{ node_custom_config }}/tacker/policy.json"
    dest: "{{ node_config_directory }}/{{ item.key }}/policy.json"
  register: tacker_policy_jsons
  when:
    - inventory_hostname in groups[item.value.group]
    - item.value.enabled | bool
    - tacker_policy.stat.exists
  with_dict: "{{ tacker_services }}"
  notify:
    - Restart tacker containers

```

But no handler named "Restart tacker containers" is defined, so when user use a custom policy file for tacker, the deployment will be failed.

zhongshengping (chdzsp)
Changed in kolla-ansible:
assignee: nobody → zhongshengping (chdzsp)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

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

Changed in kolla-ansible:
status: New → In Progress
Changed in kolla-ansible:
importance: Undecided → Medium
milestone: none → pike-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/476807
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=acecdc2cf1506811f41c53860a3ff3c673370e9a
Submitter: Jenkins
Branch: master

commit acecdc2cf1506811f41c53860a3ff3c673370e9a
Author: ZhongShengping <chdzsp@163.com>
Date: Fri Jun 23 15:23:52 2017 +0800

    The notify "Restart tacker containers" is not correct

    No handler named "Restart tacker containers", and we should restart
    the tacker container according to the context

    Change-Id: Idad8843e85eeb536d7abf8332606801f5b6e78ce
    Closes-Bug: #1700007

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b3

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.

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.