The server names in haproxy configs do not match the ip addresses

Bug #1629098 reported by Marius Cornea
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Juan Antonio Osorio Robles

Bug Description

The server names in haproxy configs do not match the ip addresses.

I'm doing a deploment with the following service allocation:

- name: Controller
  CountDefault: 1
  ServicesDefault:
    - OS::TripleO::Services::CACerts
    - OS::TripleO::Services::CinderBackup
    - OS::TripleO::Services::CinderVolume
    - OS::TripleO::Services::Core
    - OS::TripleO::Services::Kernel
    - OS::TripleO::Services::MySQL
    - OS::TripleO::Services::RabbitMQ
    - OS::TripleO::Services::HAproxy
    - OS::TripleO::Services::Keepalived
    - OS::TripleO::Services::Memcached
    - OS::TripleO::Services::Pacemaker
    - OS::TripleO::Services::Redis
    - OS::TripleO::Services::Ntp
    - OS::TripleO::Services::SwiftProxy
    - OS::TripleO::Services::Snmp
    - OS::TripleO::Services::Timezone
    - OS::Tripleo::Services::ManilaShare
    - OS::TripleO::Services::TripleoPackages
    - OS::TripleO::Services::TripleoFirewall
    - OS::TripleO::Services::SensuClient
    - OS::TripleO::Services::FluentdClient
    - OS::TripleO::Services::VipHosts

- name: ServiceApi
  CountDefault: 1
  ServicesDefault:
    - OS::TripleO::Services::CACerts
    - OS::TripleO::Services::CephMon
    - OS::TripleO::Services::CephExternal
    - OS::TripleO::Services::CephRgw
    - OS::TripleO::Services::CinderApi
    - OS::TripleO::Services::CinderScheduler
    - OS::TripleO::Services::Core
    - OS::TripleO::Services::Kernel
    - OS::TripleO::Services::Keystone
    - OS::TripleO::Services::GlanceApi
    - OS::TripleO::Services::GlanceRegistry
    - OS::TripleO::Services::HeatApi
    - OS::TripleO::Services::HeatApiCfn
    - OS::TripleO::Services::HeatApiCloudwatch
    - OS::TripleO::Services::HeatEngine
    - OS::TripleO::Services::NeutronDhcpAgent
    - OS::TripleO::Services::NeutronL3Agent
    - OS::TripleO::Services::NeutronMetadataAgent
    - OS::TripleO::Services::NeutronApi
    - OS::TripleO::Services::NeutronCorePlugin
    - OS::TripleO::Services::NeutronOvsAgent
    - OS::TripleO::Services::NovaConductor
    - OS::TripleO::Services::MongoDb
    - OS::TripleO::Services::NovaApi
    - OS::TripleO::Services::NovaMetadata
    - OS::TripleO::Services::NovaScheduler
    - OS::TripleO::Services::NovaConsoleauth
    - OS::TripleO::Services::NovaVncProxy
    - OS::TripleO::Services::Ntp
    - OS::TripleO::Services::SwiftStorage
    - OS::TripleO::Services::SwiftRingBuilder
    - OS::TripleO::Services::Snmp
    - OS::TripleO::Services::Timezone
    - OS::TripleO::Services::CeilometerApi
    - OS::TripleO::Services::CeilometerCollector
    - OS::TripleO::Services::CeilometerExpirer
    - OS::TripleO::Services::CeilometerAgentCentral
    - OS::TripleO::Services::CeilometerAgentNotification
    - OS::TripleO::Services::Horizon
    - OS::TripleO::Services::GnocchiApi
    - OS::TripleO::Services::GnocchiMetricd
    - OS::TripleO::Services::GnocchiStatsd
    - OS::Tripleo::Services::ManilaApi
    - OS::Tripleo::Services::ManilaScheduler
    - OS::Tripleo::Services::ManilaBackendGeneric
    - OS::Tripleo::Services::ManilaBackendNetapp
    - OS::Tripleo::Services::ManilaBackendCephFs
    - OS::TripleO::Services::AodhApi
    - OS::TripleO::Services::AodhEvaluator
    - OS::TripleO::Services::AodhNotifier
    - OS::TripleO::Services::AodhListener
    - OS::TripleO::Services::SaharaApi
    - OS::TripleO::Services::SaharaEngine
    - OS::TripleO::Services::IronicApi
    - OS::TripleO::Services::IronicConductor
    - OS::TripleO::Services::NovaIronic
    - OS::TripleO::Services::TripleoPackages
    - OS::TripleO::Services::TripleoFirewall
    - OS::TripleO::Services::OpenDaylight
    - OS::TripleO::Services::SensuClient
    - OS::TripleO::Services::FluentdClient
    - OS::TripleO::Services::VipHosts

This is my deploy command:

source ~/stackrc
export THT=/home/stack/templates/tripleo-heat-templates
openstack overcloud deploy --stack cloudy --templates $THT \
-e $THT/environments/network-isolation.yaml \
-e $THT/environments/network-management.yaml \
-e ~/templates/network-environment.yaml \
-e $THT/environments/storage-environment.yaml \
-e ~/templates/disk-layout.yaml \
-e $THT/environments/puppet-pacemaker.yaml \
--control-scale 3 \
--control-flavor controller \
--compute-scale 1 \
--compute-flavor compute \
--ceph-storage-scale 1 \
--ceph-storage-flavor ceph \
--ntp-server clock.redhat.com

This is my network-environment.yaml: http://paste.openstack.org/show/583549/

The server names in haproxy.cfg are called cloudy-controller-x while they point to the ip addresses of the cloud-serviceapi-x nodes, e.g:

listen aodh
  bind 10.0.0.13:8042 transparent
  bind 172.16.18.30:8042 transparent
  server cloudy-controller-0 10.0.0.25:8042 check fall 5 inter 2000 rise 2
  server cloudy-controller-1 10.0.0.23:8042 check fall 5 inter 2000 rise 2
  server cloudy-controller-2 10.0.0.17:8042 check fall 5 inter 2000 rise 2

[root@cloudy-controller-0 heat-admin]# grep cloudy-serviceapi-0.internalapi /etc/hosts
10.0.0.25 cloudy-serviceapi-0.internalapi.localdomain cloudy-serviceapi-0.internalapi

[root@cloudy-controller-0 heat-admin]# grep cloudy-controller-0.internalapi /etc/hosts
10.0.0.11 cloudy-controller-0.internalapi.localdomain cloudy-controller-0.internalapi

Expected config:
listen aodh
  bind 10.0.0.13:8042 transparent
  bind 172.16.18.30:8042 transparent
  server cloudy-serviceapi-0 10.0.0.25:8042 check fall 5 inter 2000 rise 2
  server cloudy-serviceapi-1 10.0.0.23:8042 check fall 5 inter 2000 rise 2
  server cloudy-serviceapi-2 10.0.0.17:8042 check fall 5 inter 2000 rise 2

Revision history for this message
Steven Hardy (shardy) wrote :
Revision history for this message
Marius Cornea (mcornea) wrote :
Changed in tripleo:
milestone: none → ocata-1
importance: Undecided → High
status: New → Triaged
Revision history for this message
Steven Hardy (shardy) wrote :
Changed in tripleo:
milestone: ocata-1 → newton-rc3
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
tags: added: newton-backport-potential
Steven Hardy (shardy)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Steven Hardy (shardy) wrote :
Changed in tripleo:
status: In Progress → Fix Released
tags: added: in-stable-newton
removed: newton-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 5.3.0

This issue was fixed in the openstack/puppet-tripleo 5.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 6.0.0

This issue was fixed in the openstack/puppet-tripleo 6.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.