Skip to content

Commit 4b90700

Browse files
committed
fix: limit migrate-valkey playbook
The playbook for migrating from `Redis` to `Valkey` fails as it targets `all` hosts within the inventory. This means that during reconfiguration of `Valkey` checks will fail as it attempts to perform `ping pong` against hosts outside of the `valkey` group. This has been fixed by limiting the playbook only to `valkey,redis` groups. Closes-Bug: 2158356 Change-Id: I7baeab33ca8ba4372971d51500042628e3e14efa Signed-off-by: Jack Hodgkiss <jack@stackhpc.com>
1 parent d72865e commit 4b90700

2 files changed

Lines changed: 7 additions & 1 deletion

File tree

ansible/migrate-valkey.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
- import_playbook: gather-facts.yml
33

44
- name: Perform Valkey migration
5-
hosts: all
5+
hosts: valkey,redis
66
gather_facts: false
77
max_fail_percentage: >-
88
{{ group_hosts_max_fail_percentage |
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
fixes:
3+
- |
4+
Fixes a bug where valkey migration playbook will fail as it targets hosts
5+
that are not running valkey.
6+
`LP#2158356 <https://bugs.launchpad.net/kolla-ansible/+bug/2158356>`__

0 commit comments

Comments
 (0)