openstack/openstack-ansible-os_masakari
Code Issues Proposed changes

Do not remove policy.yaml file

Browse Source 
oslo.policy can not handle policy file removal. As a result, if policy
overrides were defined at some point, but then removed, causes service
outage.

While we could add a handler trigger to restart the service
on policy removal, it's better to simplify the logic and always place an
empty policy.yaml even if no overrides are defined.

Change-Id: I2369cc870a6e60a702a54bb3fc6862fa07efb7ac
Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
This commit is contained in:
Dmitriy Rabotyagov
2025-11-14 11:56:57 +01:00
parent 52203d808a
commit 7a9dd4bd04
1 changed files with 0 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
tasks/masakari_post_install.yml
View File

@@ -56,17 +56,6 @@
mode: "0640"
config_type: yaml
when:
- masakari_policy_overrides | length > 0
- masakari_services['masakari-api']['group'] in group_names or masakari_services['masakari-engine']['group'] in group_names
tags:
- masakari-policy-override
- name: Remove legacy policy.yaml file
ansible.builtin.file:
path: "{{ masakari_etc_dir }}/policy.yaml"
state: absent
when:
- masakari_policy_overrides | length == 0
- masakari_services['masakari-api']['group'] in group_names or masakari_services['masakari-engine']['group'] in group_names
tags:
- masakari-policy-override