| 2019-04-23 11:13:41 |
Luca Miccini |
description |
I was troubleshooting a failed deployment and tracked it down to iptables rules missing for port 13778.
Looking at hieratada I found the following:
{
"138 placement": {
"dport": [
8778,
13778
]
},
that is different from the other services.
Could it be that tripleo::placement::firewall_rules in placement-api-container-puppet.yaml misses indentation (lines 104:107)?
94 outputs:
95 role_data:
96 description: Role data for the Placement API role.
97 value:
98 service_name: placement
99 config_settings:
100 map_merge:
101 - get_attr: [PlacementLogging, config_settings]
102 - apache::default_vhost: false
103 - tripleo::placement::firewall_rules:
104 '138 placement':
105 dport:
106 - 8778
107 - 13778
Looking at nova-api it would seem so:
182 tripleo::nova_api::firewall_rules:
183 '113 nova_api':
184 dport:
185 - 8774
186 - 13774 |
I was troubleshooting a failed deployment and tracked it down to iptables rules missing for port 13778.
Looking at hieratada I found the following:
{
"138 placement": {
"dport": [
8778,
13778
]
},
that is different from the other services.
Could it be that tripleo::placement::firewall_rules in placement-api-container-puppet.yaml misses indentation (lines 104:107)?
~~~
94 outputs:
95 role_data:
96 description: Role data for the Placement API role.
97 value:
98 service_name: placement
99 config_settings:
100 map_merge:
101 - get_attr: [PlacementLogging, config_settings]
102 - apache::default_vhost: false
103 - tripleo::placement::firewall_rules:
104 '138 placement':
105 dport:
106 - 8778
107 - 13778
~~~
Looking at nova-api it would seem so:
~~~
182 tripleo::nova_api::firewall_rules:
183 '113 nova_api':
184 dport:
185 - 8774
186 - 13774
~~~ |
|
