Hi Darryl
On Wed, 3 Feb 2016 at 00:39 Darryl Weaver wrote:
> This would therefore have implications for co-locating nova-compute with
> ceph charms on physical nodes.
> Upgrading nova-compute would update the apt repository regardless of what
> the ceph charm is doing.
>
Yes - this is one of th
On Mon, 1 Feb 2016 at 15:04 Darryl Weaver wrote:
> 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
>
Currently the behaviour of changing the source config option on t
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 wrote:
>
> Is upgrading ceph from one so
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@maascontroller:~$ juju upgrade-charm ceph
Added charm "cs:trusty/ceph-43" to the environment.
and then:
ubuntu@maascontroller:~$ juju set ceph source=cloud:trust
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 a
On Fri, Jan 29, 2016 at 9:43 AM Pshem Kowalczyk 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 a
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 wrote:
> Ok,
>
> force-downgrade doesn't seem to work:
> ubuntu@maascontroller:~$ juju upgrade-charm keystone
>
>
>
> ERRO
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
This is what I get:
ubuntu@maascontroller:~$ juju upgrade-charm --force keystone
2016/01/29 10:43:02 warning: discarding cookies in invalid format (error:
json: cannot unmarshal object into Go value of type []cookiejar.entry)
2016/01/29 10:43:04 warning: discarding cookies in invalid format (error
Hi Pshem
On Thu, 28 Jan 2016 at 22:39 Pshem Kowalczyk 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
Hi,
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
11 matches
Mail list logo
