[Bug 1585109] Fix merged to charm-keystone (master)

[OpenStack Infra]

Reviewed:  https://review.openstack.org/320344
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=e40f8ea5e4fd92db6e2d405271953a89540bea34
Submitter: Jenkins
Branch:    master

commit e40f8ea5e4fd92db6e2d405271953a89540bea34
Author: Andrey Pavlov <andrey-mp at yandex.ru>
Date:   Tue May 24 13:26:36 2016 +0300

    Ensure service port is opened for access.
    
    In the case where the keystone service is exposed, Juju needs
    to know which ports should be opened. Ensure that the service
    port is opened so that remote access can be made in providers
    that implement machine fire-walling such as ec2.
    
    Change-Id: I15a1e613f6b049e7c7e2c89d5bb94bdfb5da39ac
    Closes-Bug: #1585109

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1585109

Title:
  Charm do not open public port

Status in cinder package in Juju Charms Collection:
  Fix Committed
Status in keystone package in Juju Charms Collection:
  Fix Committed

Bug description:
  Keystone and cinder charms should open their ports to allow clients to
  connect.

  Nova and glance charms already do this.

  I deploy OpenStack by Juju in Amazon (without containers) and after deployment I can't work with this deployment.
  All services are exposed.
  But only nova and glance opens their ports in this case - 3333,8773,8774 and 9292.

  I can reach nova but nova can't reach keystone for auth for example.
  I can't reach keystone for any operation.

  I work with trusty series charms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charms/+source/cinder/+bug/1585109/+subscriptions