Pshem,

I'm curious if switching would work for you...

e.g. juju upgrade-charm --switch cs:trusty/glance-29

Thanks,

Billy

On Thu, Jan 28, 2016 at 3:43 PM, 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.
>
> 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
>
>


-- 
Billy Olsen

billy.ol...@canonical.com
Software Engineer
Canonical USA
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to