Fix misnaming of service in firewall rule

On Octavia-enabled composable role deployments where the Octavia health
manager service doesn't run co-located with the API service, the
firewall rule to allow messages in to the o-hm0 interface was not being
created. As a result of that, the load balancers were not going ONLINE.

Conflicts:
    puppet/services/octavia-health-manager.yaml

Closes-Bug: #1808190
Depends-On: https://review.openstack.org/#/c/624403/
Change-Id: Icc568a551b902e6d9f003250226468ed38a776fc
(cherry picked from commit 29da33fae2)
This commit is contained in:
Carlos Goncalves 2018-12-12 18:06:34 +01:00
parent a19a0b0ad8
commit a74808fafd
2 changed files with 5 additions and 1 deletions

View File

@ -79,7 +79,7 @@ outputs:
- get_attr: [OctaviaBase, role_data, config_settings]
- octavia::health_manager::heartbeat_key: {get_param: OctaviaHeartbeatKey}
octavia::health_manager::event_streamer_driver: {get_param: OctaviaEventStreamerDriver}
tripleo.octavia_api.firewall_rules:
tripleo.octavia_health_manager.firewall_rules:
'200 octavia health manager interface':
proto: udp
dport: 5555

View File

@ -0,0 +1,4 @@
---
issues:
- Fix misnaming of service in firewall rule for Octavia Health Manager
service.