Fix telemetry keepalived VIP interface
management network, which is used for communication with
telemetry api, is bound to ens4 interface, so mgmt VIP also
should be bound to ens4 interface.
Change-Id: I360885f9b4ed918452855afe95d9e39230748319
Related-Prod: https://mirantis.jira.com/browse/PROD-18938
diff --git a/classes/cluster/virtual-mcp-pike-ovs/openstack/telemetry.yml b/classes/cluster/virtual-mcp-pike-ovs/openstack/telemetry.yml
index 513ae52..62ded65 100644
--- a/classes/cluster/virtual-mcp-pike-ovs/openstack/telemetry.yml
+++ b/classes/cluster/virtual-mcp-pike-ovs/openstack/telemetry.yml
@@ -27,7 +27,7 @@
gnocchi_statsd_resource_id: 07f26121-5777-48ba-8a0b-d70468133dd9
keepalived_openstack_telemetry_vip_address: ${_param:openstack_telemetry_address}
keepalived_openstack_telemetry_vip_password: ${_param:openstack_telemetry_keepalived_password}
- keepalived_openstack_telemetry_vip_interface: ens3
+ keepalived_openstack_telemetry_vip_interface: ens4
cluster_vip_address: ${_param:openstack_telemetry_address}
cluster_local_address: ${_param:single_address}
cluster_node01_hostname: ${_param:openstack_telemetry_node01_hostname}