Comment 2 for bug 1477137

use of stopstart=true should fix this up

On Wed, Dec 2, 2015 at 11:13 AM, Edward Hope-Morley <
<email address hidden>> wrote:

> ** Changed in: glance (Juju Charms Collection)
> Assignee: (unassigned) => Edward Hope-Morley (hopem)
>
> ** Changed in: keystone (Juju Charms Collection)
> Assignee: (unassigned) => Edward Hope-Morley (hopem)
>
> ** Changed in: glance (Juju Charms Collection)
> Status: Triaged => In Progress
>
> ** Changed in: keystone (Juju Charms Collection)
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are a member of OpenStack
> Charmers, which is subscribed to glance in Juju Charms Collection.
> https://bugs.launchpad.net/bugs/1477137
>
> Title:
> when enabling ssl need to restart keystone before apache
>
> Status in glance package in Juju Charms Collection:
> In Progress
> Status in keystone package in Juju Charms Collection:
> In Progress
>
> Bug description:
> If i deploy keystone in http mode (use-https=no, https-service-
> endpoints=False) then I enable https, i get an error [1] in the leader
> unit because the charm wants to connect to keystone on port 35337 yet
> keystone is still listening on 35347 because it was not restarted
> after its conf file was changed. Result is that apache wants to claim
> port 35347 and forward to keystone on 35337 but keystone was not
> properly restarted when its admin_port was changed so apache fails to
> start. This is resolved by simply restarting keystone then apache and
> in that order.
>
> [1] http://paste.ubuntu.com/11919790/
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/glance/+bug/1477137/+subscriptions
>