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 commit29da33fae2
) (cherry picked from commita74808fafd
)
This commit is contained in:
parent
982436b346
commit
a68197ba75
|
@ -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
|
||||
|
|
|
@ -0,0 +1,4 @@
|
|||
---
|
||||
issues:
|
||||
- Fix misnaming of service in firewall rule for Octavia Health Manager
|
||||
service.
|
Loading…
Reference in New Issue