Juju Charms Collection
ceilometer package

ceilometer-next amulet test fails with "port:8767 != expected port:8777"

Bug #1440758 reported by Ryan Beisner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ceilometer (Juju Charms Collection)
Fix Released
Undecided
Unassigned

Bug Description

ceilometer-next amulet test fails with: ceilometer config error: section [api] port:8767 != expected port:8777

The test_ceilometer_config method in basic_deployment.py checks the ceilometer config file via validate_config_data in charmhelpers, expecting ceilometer to be listening on 8777. Ceilometer is actually listening on 8767, with haproxy in front of it on 8777.

revno:
75
Lightweight checkout (format: 2a)
Location:
  light checkout root: /var/lib/jenkins/checkout/ceilometer
   checkout of branch: bzr+ssh://bazaar.launchpad.net/~openstack-charmers/charms/trusty/ceilometer/next

See original description

Related branches

lp://qastaging/~openstack-charmers-archive/charms/trusty/ceilometer/next
lp://qastaging/~1chb1n/charms/trusty/ceilometer/next-amulet-fix-lp1440758
Corey Bryant (community): Approve
charmers: Pending requested
Diff: 21 lines (+2/-2)
1 file modified
tests/basic_deployment.py (+2/-2)
charmers: Pending requested
Diff: 3219 lines (+2437/-132) (has conflicts)
45 files modified
Makefile (+12/-2)
README.md (+2/-1)
charm-helpers-tests.yaml (+5/-0)
config.yaml (+6/-0)
hooks/ceilometer_hooks.py (+25/-0)
hooks/ceilometer_utils.py (+3/-2)
hooks/charmhelpers/contrib/charmsupport/nrpe.py (+41/-7)
hooks/charmhelpers/contrib/hahelpers/cluster.py (+5/-1)
hooks/charmhelpers/contrib/network/ip.py (+84/-1)
hooks/charmhelpers/contrib/openstack/amulet/deployment.py (+5/-2)
hooks/charmhelpers/contrib/openstack/context.py (+108/-9)
hooks/charmhelpers/contrib/openstack/files/__init__.py (+18/-0)
hooks/charmhelpers/contrib/openstack/files/check_haproxy.sh (+32/-0)
hooks/charmhelpers/contrib/openstack/files/check_haproxy_queue_depth.sh (+30/-0)
hooks/charmhelpers/contrib/openstack/ip.py (+37/-0)
hooks/charmhelpers/contrib/openstack/neutron.py (+70/-0)
hooks/charmhelpers/contrib/openstack/templates/zeromq (+14/-0)
hooks/charmhelpers/contrib/openstack/utils.py (+7/-72)
hooks/charmhelpers/contrib/python/packages.py (+2/-2)
hooks/charmhelpers/core/fstab.py (+4/-4)
hooks/charmhelpers/core/hookenv.py (+26/-0)
hooks/charmhelpers/core/host.py (+10/-6)
hooks/charmhelpers/core/services/helpers.py (+12/-4)
hooks/charmhelpers/core/strutils.py (+42/-0)
hooks/charmhelpers/core/sysctl.py (+2/-2)
hooks/charmhelpers/core/templating.py (+3/-3)
hooks/charmhelpers/core/unitdata.py (+477/-0)
hooks/charmhelpers/fetch/archiveurl.py (+10/-10)
hooks/charmhelpers/fetch/giturl.py (+1/-1)
templates/icehouse/ceilometer.conf (+9/-3)
tests/00-setup (+11/-0)
tests/14-basic-precise-icehouse (+11/-0)
tests/15-basic-trusty-icehouse (+9/-0)
tests/16-basic-trusty-juno (+11/-0)
tests/README (+53/-0)
tests/basic_deployment.py (+330/-0)
tests/charmhelpers/__init__.py (+38/-0)
tests/charmhelpers/contrib/__init__.py (+15/-0)
tests/charmhelpers/contrib/amulet/__init__.py (+15/-0)
tests/charmhelpers/contrib/amulet/deployment.py (+93/-0)
tests/charmhelpers/contrib/amulet/utils.py (+314/-0)
tests/charmhelpers/contrib/openstack/__init__.py (+15/-0)
tests/charmhelpers/contrib/openstack/amulet/__init__.py (+15/-0)
tests/charmhelpers/contrib/openstack/amulet/deployment.py (+111/-0)
tests/charmhelpers/contrib/openstack/amulet/utils.py (+294/-0)
Ryan Beisner (1chb1n)
description: updated
Revision history for this message
Ryan Beisner (1chb1n) wrote :

I think the test needs to be adjusted to expect 8767, as haproxy sits on 8777, in front of ceilometer which is at 8767.

## /etc/ceilometer/ceilometer.conf defines api as:
[api]
port = 8767

## things listening on the ceilometer unit:
$ sudo netstat -taupn | grep LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 7549/apache2
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 836/sshd
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 7686/haproxy
tcp 0 0 0.0.0.0:8767 0.0.0.0:* LISTEN 11982/python
tcp 0 0 0.0.0.0:8777 0.0.0.0:* LISTEN 7686/haproxy
tcp6 0 0 :::22 :::* LISTEN 836/sshd

## /etc/haproxy/haproxy.cfg part:
frontend tcp-in_ceilometer_api
    bind *:8777
    acl net_172.17.108.69 dst 172.17.108.69/255.255.255.0
    use_backend ceilometer_api_172.17.108.69 if net_172.17.108.69
    default_backend ceilometer_api_172.17.108.69

backend ceilometer_api_172.17.108.69
    balance leastconn
    server ceilometer-0 172.17.108.69:8767 check

## version info:
$ dpkg-query --show ceilometer-common python-ceilometer python-ceilometerclient
ceilometer-common 2014.1.3-0ubuntu1~cloud0
python-ceilometer 2014.1.3-0ubuntu1~cloud0
python-ceilometerclient 1.0.8-0ubuntu1~cloud0

## just fyi:
$ keystone catalog
/usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: DeprecationWarning: The keystone CLI is deprecated in favor of python-openstackclient. For a Python library, continue using python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
Service: metering
+-------------+----------------------------------+
| Property | Value |
 +-------------+----------------------------------+
| adminURL | http://172.17.108.69:8777 |
| id | 51b87e2a28d046db85dd6916371aafd4 |
| internalURL | http://172.17.108.69:8777 |
| publicURL | http://172.17.108.69:8777 |
| region | RegionOne |
 +-------------+----------------------------------+
Service: identity
+-------------+----------------------------------+
| Property | Value |
 +-------------+----------------------------------+
| adminURL | http://172.17.108.70:35357/v2.0 |
| id | 091c10e5a6d541d4a46ce3de84e954b2 |
| internalURL | http://172.17.108.70:5000/v2.0 |
| publicURL | http://172.17.108.70:5000/v2.0 |
| region | RegionOne |
 +-------------+----------------------------------+

Ryan Beisner (1chb1n)
description: updated
Revision history for this message
Ryan Beisner (1chb1n) wrote :

FYI, near as I can tell, haproxy came into the picture for single nodes here:
http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/ceilometer/next/revision/67.2.4

Liam Young (gnuoy)
Changed in ceilometer (Juju Charms Collection):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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