From 0b3b148d6d2c31edb20e80adc3ba3662fdfaf5ab Mon Sep 17 00:00:00 2001 From: Matt Crees Date: Thu, 27 Feb 2025 12:07:42 +0000 Subject: [PATCH] Fix handler notify in fix-houston.yml The handler was changed when we fixed linting, but the notify wasn't updated. --- etc/kayobe/ansible/fix-houston.yml | 2 +- .../notes/fix-fix-houston-notify-165a7871bda48f68.yaml | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-) create mode 100644 releasenotes/notes/fix-fix-houston-notify-165a7871bda48f68.yaml diff --git a/etc/kayobe/ansible/fix-houston.yml b/etc/kayobe/ansible/fix-houston.yml index 0333450e7..9dfdc924f 100644 --- a/etc/kayobe/ansible/fix-houston.yml +++ b/etc/kayobe/ansible/fix-houston.yml @@ -29,7 +29,7 @@ vars: interface_name: "{{ item }}" when: neutron_bridge_name | length > 0 - notify: reload systemd + notify: Reload systemd - name: Enable and start systemd service for -ovs network interface ansible.builtin.systemd: diff --git a/releasenotes/notes/fix-fix-houston-notify-165a7871bda48f68.yaml b/releasenotes/notes/fix-fix-houston-notify-165a7871bda48f68.yaml new file mode 100644 index 000000000..a7e12a0e2 --- /dev/null +++ b/releasenotes/notes/fix-fix-houston-notify-165a7871bda48f68.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixes an issue where the fix-houston.yml playbook would fail to reload + systemd as the ``notify`` statement was incorrect.