Upgrading charms to 16.01 - Ceph
Darryl Weaver
darryl at ubuntu.com
Mon Feb 1 14:29:48 UTC 2016
Hi Pshem,
I've seen that bug too and just tested a kilo to liberty upgrade in my lab.
So, I've submitted a bug report here:
https://bugs.launchpad.net/charms/+source/ceph/+bug/1540376
Feel free to add to it.
On 29 January 2016 at 02:17, Pshem Kowalczyk <pshem.k at gmail.com> wrote:
>
> Is upgrading ceph from one source to the other supported as well, or does
> the source only work for new deployments?
>
> I did this:
> ubuntu at maascontroller:~$ juju upgrade-charm ceph
> Added charm "cs:trusty/ceph-43" to the environment.
>
> and then:
> ubuntu at maascontroller:~$ juju set ceph source=cloud:trusty-mitaka
>
> but that didn't really upgrade ceph (monitors in my case):
> root at juju-machine-0-lxc-0:~# ceph -v
> ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)
>
> root at juju-machine-0-lxc-0:~# dpkg -l | grep ceph
> ii ceph 0.94.5-0ubuntu0.15.10.1~cloud0
> amd64 distributed storage and file system
> ii ceph-common 0.94.5-0ubuntu0.15.10.1~cloud0
> amd64 common utilities to mount and interact with a ceph storage
> cluster
> ii libcephfs1 0.94.5-0ubuntu0.15.10.1~cloud0
> amd64 Ceph distributed file system client library
> ii python-ceph 0.94.5-0ubuntu0.15.10.1~cloud0 all
> Meta-package for python libraries for the Ceph libraries
> ii python-cephfs 0.94.5-0ubuntu0.15.10.1~cloud0
> amd64 Python libraries for the Ceph libcephfs library
>
> I've jumped onto each machine and manually updated the source to:
> deb http://ubuntu-cloud.archive.canonical.com/ubuntu
> trusty-updates/mitaka main
>
> and then dist-upgraded the machine and it updated as expected to 9.2:
>
> root at juju-machine-0-lxc-0:~# ceph -v
> ceph version 9.2.0 (bb2ecea240f3a1d525bcb35670cb07bd1f0ca299)
>
>
>
> On Fri, 29 Jan 2016 at 13:15 Pshem Kowalczyk <pshem.k at gmail.com> wrote:
>
>>
>> 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.nelson at canonical.com>
>> wrote:
>>
>>> On Fri, Jan 29, 2016 at 9:43 AM Pshem Kowalczyk <pshem.k at gmail.com>
>>> wrote:
>>>
>>>> Ok,
>>>>
>>>> force-downgrade doesn't seem to work:
>>>> ubuntu at maascontroller:~$ juju upgrade-charm keystone
>>>>
>>>>
>>>>
>>>> ERROR already running latest charm "cs:trusty/keystone-33"
>>>> ubuntu at 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 at maascontroller:~$ juju set glance
>>>> openstack-origin=cloud:trusty-mitaka
>>>> ubuntu at 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.page at ubuntu.com> wrote:
>>>>
>>>>>
>>>>> Hi Pshem
>>>>>
>>>>> On Thu, 28 Jan 2016 at 22:39 Pshem Kowalczyk <pshem.k at 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 at lists.ubuntu.com
>>>>> Modify settings or unsubscribe at:
>>>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>>>
>>>> --
>>>> Juju mailing list
>>>> Juju at lists.ubuntu.com
>>>> Modify settings or unsubscribe at:
>>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>>
>>>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
--
Best Wishes,
Darryl Weaver
+44 (0)7770 968825
darryl at ubuntu.com
IRC: dweaver on Freenode, #ubuntu-uk or #darrylweaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160201/fc344a68/attachment.html>
More information about the Juju
mailing list