Hi All,
We at Veritas Technologies LLC are trying to deploy juju based OpenStack Pike
bits, from location:
https://jujucharms.com/u/openstack-charmers-next/openstack-base-xenial-pike/ .
But it fails at keystone charm in 'shared-db-relation-changed' hook giving
following stack trace:
*
Hi Akshay
I think you've tripped over:
https://bugs.launchpad.net/charm-keystone/+bug/1722909
which I did as well last night - this only impacts the development version
of the charm which you are using with the bundle.
I have a fix up for this, should land in the next couple of hours (we've
b
Copying in the Juju list also
On 12/10/17 22:18, Ian Booth wrote:
> I'd like to understand the use case you have in mind a little better. The
> premise of the network-get output is that charms should not think about public
> vs private addresses in terms of what to put into relation data - the oth
Hi All,
> I think the inability to remove a model that is half-dead might be fixed
already in 2.3 but has to do with an issue around 2 critical documents that
define a model, and one of them has been removed but not the other, which
leads to a bunch of code that gets a different view of whether th
So just changing your client isn't going to fix the issue, as it is a
server side issue that is refusing to destroy the models.
https://bugs.launchpad.net/bugs/1714409
Is at least one of them that might be relevant for your issue.
I also know that we have:
https://bugs.launchpad.net/bugs/172178
> So just changing your client isn't going to fix the issue, as it is a
server side issue that is refusing to destroy the models.
Aha. That makes more sense, actually.
I'll look forward to testing things out once things update on the JaaS side
:-)
~ PeteVG
On Thu, Oct 12, 2017 at 3:46 PM John M
