I worked it out as well :-) My final workflow is this (for charms that support the openstack-upgrade action):
1. Set the managed upgrade flag action-managed-upgrade=true 2. upgrade the charm: juju upgrade-charm 3. Set new origin openstack-origin=cloud:trusty-mitaka 4. uprade each unit juju action do unit/0 openstack-upgrade kind regards Pshem On Fri, 29 Jan 2016 at 12:34 Michael Nelson <michael.nel...@canonical.com> wrote: > On Fri, Jan 29, 2016 at 9:43 AM Pshem Kowalczyk <pshe...@gmail.com> wrote: > >> Ok, >> >> force-downgrade doesn't seem to work: >> ubuntu@maascontroller:~$ juju upgrade-charm keystone >> >> >> >> ERROR already running latest charm "cs:trusty/keystone-33" >> ubuntu@maascontroller:~$ juju upgrade-charm --force keystone >> ERROR already running latest charm "cs:trusty/keystone-33" >> >> I ended up removing each unit and re-adding it. This has resolved the >> keystone issue. >> >> I have tried that method with another charm (glance): >> >> ubuntu@maascontroller:~$ juju set glance >> openstack-origin=cloud:trusty-mitaka >> ubuntu@maascontroller:~$ juju upgrade-charm --force glance >> Added charm "cs:trusty/glance-30" to >> the environment. >> >> that has resulted in exactly the same error: >> 2016-01-28 22:40:39 ERROR juju-log FATAL ERROR: Could not derive >> OpenStack version for codename: mitaka >> 2016-01-28 22:40:39 ERROR juju.worker.uniter.operation runhook.go:107 >> hook "config-changed" failed: exit status 1 >> >> So I think the only way is to blew away a service unit and deploy a new >> one. >> > > James' point above was that you need to upgrade the charm *before* you set > the config to use mitaka. The error you are seeing above is on > config-changed before the charm upgrade even happens, as the old charm > doesn't know about mitaka. > > If you haven't already blown away your glance service, you can set the > openstack-origin back for glance, resolve the config-changed error, then do > the upgrade first.. > > >> >> kind regards >> Pshem >> >> >> On Fri, 29 Jan 2016 at 10:49 James Page <james.p...@ubuntu.com> wrote: >> >>> >>> Hi Pshem >>> >>> On Thu, 28 Jan 2016 at 22:39 Pshem Kowalczyk <pshe...@gmail.com> wrote: >>> >>>> I've tried to upgrade keystone to the new charm version (from liberty). >>>> I've updated the source: >>>> >>>> juju set keystone openstack-origin=cloud:trusty-mitaka >>>> >>>> and scheduled an upgrade: >>>> >>>> juju upgrade charm keystone >>>> >>>> but the charm upgrade fails: >>>> >>>> 2016-01-28 21:36:13 ERROR juju-log FATAL ERROR: Could not derive >>>> OpenStack version for codename: mitaka >>>> >>>> What am I doing wrong? >>>> >>> >>> You need to upgrade the charm first, and then set the configuration >>> option as the old version of the charm does not know about mitaka. >>> >>> You can resolve this by doing: >>> >>> juju upgrade-charm --force keystone >>> juju resolved --retry keystone/0 (or whatever the unit name is that >>> failed) >>> >>> Hopefully that should fix you up. >>> >>> Cheers >>> >>> James >>> -- >>> Juju mailing list >>> Juju@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/juju >>> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju