From 3ecad17ed76ce850afedac0bf30c51512eda7a1b Mon Sep 17 00:00:00 2001 From: ramishra Date: Tue, 1 Jun 2021 14:44:56 +0530 Subject: [PATCH] Map RedisVipPort and OVNDBsVipPort to OS::Heat::None As we use PATCH update if we remove these resources from default resource registry the existing mappings would still be there in the stack environment. Map them to OS::Heat::None instead. Depends-On: https://review.opendev.org/c/openstack/python-tripleoclient/+/793909 Change-Id: I526dff594543df025215c6af476be46e948c9fe5 --- overcloud-resource-registry-puppet.j2.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/overcloud-resource-registry-puppet.j2.yaml b/overcloud-resource-registry-puppet.j2.yaml index d03de9c190..3ef34fcbff 100644 --- a/overcloud-resource-registry-puppet.j2.yaml +++ b/overcloud-resource-registry-puppet.j2.yaml @@ -82,6 +82,9 @@ resource_registry: OS::TripleO::Network::Ports::NetIpMap: network/ports/net_ip_map.yaml OS::TripleO::Network::Ports::NetIpListMap: network/ports/net_ip_list_map.yaml + OS::TripleO::Network::Ports::RedisVipPort: OS::Heat::None + OS::TripleO::Network::Ports::OVNDBsVipPort: OS::Heat::None + # Port assignments for the VIPs {%- for network in networks if network.vip|default(false) and network.enabled|default(true) %} OS::TripleO::Network::Ports::{{network.name}}VipPort: network/ports/noop.yaml