Haproxy config for nova metadata uses ctlplane ip addresses instead of internal_api when using network isolation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Juan Antonio Osorio Robles |
Bug Description
Haproxy config for nova metadata uses ctlplane ip addresses instead of internal_api when using network isolation:
[root@overcloud
listen nova_metadata
bind 192.168.0.15:8775 transparent
server overcloud-
server overcloud-
server overcloud-
The endpointmap shows the NovaMetadataNetwork is set to internal_api:
[stack@undercloud ~]$ openstack stack show overcloud-
WARNING: openstackclient
| | u''NovaMetadata
But on the controller nodes there's not hieradata which sets the addresses to the internal_api network:
[root@overcloud
nil
[root@overcloud
nil
The deploy command:
source ~/stackrc
export THT=~/templates
openstack overcloud deploy --templates $THT \
-e $THT/environmen
-e $THT/environmen
-e ~/templates/
-e $THT/environmen
-e ~/templates/
-e $THT/environmen
--control-scale 3 \
--control-flavor controller \
--compute-scale 1 \
--compute-flavor compute \
--ceph-
--ceph-
--ntp-server clock.redhat.com \
--libvirt-type qemu
[stack@undercloud ~]$ cat templates/
resource_registry:
OS::TripleO:
OS::TripleO:
OS::TripleO:
parameter_defaults:
InternalApiNe
InternalApiAl
InternalApiNe
StorageNetCidr: 10.0.0.128/25
StorageAlloca
StorageNetwor
StorageMgmtNe
StorageMgmtAl
StorageMgmtNe
TenantNetCidr: 10.0.1.128/25
TenantAllocat
ManagementNet
ManagementAll
ExternalNetCidr: 172.16.18.0/25
ExternalAlloc
ExternalInter
ExternalNetwo
ControlPlaneS
ControlPlaneD
EC2MetadataIp: 192.168.0.1
DnsServers: ["10.16.
NeutronExtern
NeutronBridge
NeutronEnable
NeutronNetwor
NeutronTunnel
NeutronNetwor
NeutronGlobal
Fix proposed to branch: master /review. openstack. org/373141
Review: https:/