I've seen this and then it clears on the next update-status hook. Maybe the
internal status update code is not being executed for the relevant hook?
On 5 Jan 2017 10:31 am, "James Page" <email address hidden> wrote:
> Message is:
>
> message: 'Ports which should be open, but are not: 5000, 35357'
>
> haproxy is running, but not listening on either port.
>
> --
> You received this bug notification because you are a member of OpenStack
> Charmers, which is subscribed to keystone in Juju Charms Collection.
> https://bugs.launchpad.net/bugs/1648396
>
> Title:
> Deployment of Keystone cluster often fails due to haproxy service not
> being started
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charms/+source/keystone/+bug/
> 1648396/+subscriptions
>
I've seen this and then it clears on the next update-status hook. Maybe the
internal status update code is not being executed for the relevant hook?
On 5 Jan 2017 10:31 am, "James Page" <email address hidden> wrote:
> Message is: /bugs.launchpad .net/bugs/ 1648396 /bugs.launchpad .net/charms/ +source/ keystone/ +bug/ +subscriptions
>
> message: 'Ports which should be open, but are not: 5000, 35357'
>
> haproxy is running, but not listening on either port.
>
> --
> You received this bug notification because you are a member of OpenStack
> Charmers, which is subscribed to keystone in Juju Charms Collection.
> https:/
>
> Title:
> Deployment of Keystone cluster often fails due to haproxy service not
> being started
>
> To manage notifications about this bug go to:
> https:/
> 1648396/
>