Comment 4 for bug 1408902

Ed, I think the problem is different in the stable version of the charms. In the next branches, this is possibly an issue - however in the cases I've seen this issue encountered there is no issue in binding to the ssl port, rather the Apache virtual server is configured to listen on a public endpoint. This is due to not having any of the os-xxx-networks defined - the call on http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/contrib/openstack/context.py#L626 will simply return the default private address for the unit, which happens to be the hostname and apache does not start the ssl listening for this particular port.