Juju Charms Collection
rabbitmq-server package

default management ui port changed in > 3.0

Bug #1651195 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack RabbitMQ Server Charm
Fix Released
Medium
Liam Young
OpenStack RabbitMQ Server Charm 17.02
rabbitmq-server (Juju Charms Collection)
Invalid
Medium
Liam Young
Juju Charms Collection 17.01

Bug Description

Rabbitmq management gui port is no longer correct for rabbitmq > 3.0. For releases following 3.0 we need to configure the rabbitmq-server charm to use 15672 instead of (currently) 55672.

See https://www.rabbitmq.com/management.html under getting started.

Revision history for this message
james beedy (jamesbeedy) wrote :
Liam Young (gnuoy)
Changed in rabbitmq-server (Juju Charms Collection):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Liam Young (gnuoy)
milestone: none → 17.01
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-rabbitmq-server (master)

Fix proposed to branch: master
Review: https://review.openstack.org/428234

Changed in rabbitmq-server (Juju Charms Collection):
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-rabbitmq-server (master)

Reviewed: https://review.openstack.org/428234
Committed: https://git.openstack.org/cgit/openstack/charm-rabbitmq-server/commit/?id=82a92a6d5d5f1a6887e9b6df45ca0e26db890b6b
Submitter: Jenkins
Branch: master

commit 82a92a6d5d5f1a6887e9b6df45ca0e26db890b6b
Author: Liam Young <email address hidden>
Date: Thu Feb 2 16:09:09 2017 +0000

    Correct port that is exposed for management

    For rabbitmq-server version 3+ (Trusty and above) the managment
    port is 15672, however the charm exposes the old port 55672. This
    change fixes that behaviour. Fwiw the amulet tests are already
    expecting the managment interface to be 15672 but tests run with the
    OpenStack providor and would have missed that this port was not
    being exposed.

    Change-Id: Ia61d1c12df9300408d33a1768f546c38b33c5677
    Closes-Bug: 1651195

Changed in rabbitmq-server (Juju Charms Collection):
status: In Progress → Fix Committed
James Page (james-page)
Changed in charm-rabbitmq-server:
assignee: nobody → Liam Young (gnuoy)
importance: Undecided → Medium
status: New → Fix Committed
Changed in rabbitmq-server (Juju Charms Collection):
status: Fix Committed → Invalid
James Page (james-page)
Changed in charm-rabbitmq-server:
milestone: none → 17.02
James Page (james-page)
Changed in charm-rabbitmq-server:
status: Fix Committed → 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.