[01:41] Hi, I hit this issue: https://bugs.launchpad.net/charms/+source/neutron-api/+bug/1535374, is there a way to update the keystone charm without redeploy? [01:41] Bug #1535374: keystone hook failed: "shared-db-relation-changed" - Invalid service requested: 'neutron'

[01:41] how do I tell the unit to update the keystone charm from the keystone/next? === sarnold is now known as | === | is now known as sarnold [02:05] catbus1: I am on my way out but saw your question. Have you take a look at charm upgrade? [02:06] re the bug you referenced the suggestion was to try the next development release of the charm and not the stable one. But not that around Jan 28 there should be openstack charm release to pull this in [02:06] catbus1: references to look at: [02:06] https://jujucharms.com/docs/1.25/authors-charm-upgrades [02:06] arosales: but the charm upgrade is from the same place keystone/stable, right? I need it from keystone/next [02:07] correct you would need to branch the charm locally and then specify that in your charm upgrade [02:07] here are a couple of other references [02:07] https://jujucharms.com/docs/1.24/commands (search the page for upgrade-charm [02:07] arosales: ok, great, thank you! [02:07] and a few other forum posts [02:07] http://marcoceppi.com/2015/01/force-upgrade-best-juju-secret/ [02:07] https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes/OpenStackCharms [02:07] https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1510 [02:08] if you are running in production I would suggest to wait for the stable release so you are on a stablel to stable path [02:08] but at least you can read over these options and perhaps give you some things to consider [02:08] hope that helps. [02:08] have a good weekend [02:08] * arosales grabs some dinner [02:08] arosales: it does help. thanks, have a weekend. [02:09] cool === urulama__ is now known as urulama [15:51] * D4RKS1D3 Hi