** Changed in: ceph-osd (Juju Charms Collection)
Status: Incomplete => Triaged
** Changed in: ceph-osd (Juju Charms Collection)
Assignee: Jorge Niedbalski (niedbalski) => (unassigned)
** Changed in: ceph-osd (Juju Charms Collection)
Milestone: None => 17.01
** No longer affects:
** Changed in: ceph-osd (Juju Charms Collection)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to Mitaka "misses"
Marking Ubuntu task as invalid - this problem its not in the packaging.
** Changed in: ceph (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
(just a hunch but I suspect your ceph-mon units never actually
upgraded).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to Mitaka "misses" /var/lib/ceph
Hmm I wonder whether this is due to the co-location of ceph-osd with
nova-compute; which order did you perform the upgrade in? switching
openstack-origin on the nova-compute node will trigger a package upgrade
for all packages on the machine, including ceph.
ceph-osd can be more selective, so
ditto on ceph-osd:
2016-08-10 11:13:17 INFO juju-log old_version: cloud:trusty-kilo
2016-08-10 11:13:17 INFO juju-log new_version: cloud:trusty-mitaka
2016-08-10 11:13:18 INFO juju-log Invalid upgrade path from cloud:trusty-kilo
to cloud:trusty-mitaka. Valid paths are: ['cloud:trusty-liberty ->
ceph-mon log for direct upgrade attempt:
2016-08-10 11:10:27 INFO juju-log old_version: cloud:trusty-kilo
2016-08-10 11:10:27 INFO juju-log new_version: cloud:trusty-mitaka
2016-08-10 11:10:27 INFO juju-log Invalid upgrade path from cloud:trusty-kilo
to cloud:trusty-mitaka. Valid paths are:
Hi Rafael
I tried reproducing your issue this morning - found a different problem
(bug 1611719) but that's unrelated to this - I did end up with a ceph
deployment that had the correct permissions.
I deployed trusty-kilo; upgraded to trusty-liberty and then to trusty-
mitaka.
--
You received
I see you appear to go direct from kilo->mitaka
I'll try that and see if that makes a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to
Interestingly the packaging should be trying to make some directory
changes:
# 5. adjust file and directory permissions
if ! dpkg-statoverride --list $SERVER_HOME >/dev/null
then
chown $SERVER_USER:$SERVER_GROUP $SERVER_HOME
chmod u=rwx,g=rx,o=
Ok I just re-deployed everything.
After I finished upgrade, I rebooted all the environment.
After ceph machines came back, I had:
https://pastebin.canonical.com/162720/
So I guess something is wrong... 2nd time I was able to reproduce the
same behaviour.
When changing permissions:
juju ssh
Hello James,
I'm creating and destroying this deployment every day (trying to
reproduce other bug). For this particular error, the environment was
created a few hours before using:
$ cat ceph-osd.yaml
ceph-osd:
source: 'cloud:trusty-proposed/kilo'
osd-devices: /dev/vdb
osd-reformat:
I'm re-deploying everything again.. upgrading nova-compute right now.
Will update ceph again in a few more minutes. Let me know if you need
anything from my setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Rafael
Which charm versions where you using? the ownership during upgrade
change only just landed in the stable charms (as of end of July) so is
it possible that you had an older charm version at the point of ceph
upgrade?
** Changed in: ceph (Ubuntu)
Status: New => Opinion
--
You
Actually the package *can't* do this - the packaging is configured not
to restart or attempt to manage the ceph daemons during normal package
updates; the reason being is that you need to co-ordinate this just
like any other outage, and doing it during a package upgrade is not
ideal and can cause
+1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to Mitaka "misses" /var/lib/ceph
ownership change
To manage notifications about this bug go to:
I actually committed a fix for this. I hit this also myself. Here's
the patch: https://review.openstack.org/#/c/345646/ for ceph-mon and
https://review.openstack.org/#/c/345647/ for ceph-osd. Just be aware
that if you have a lot of data in your cluster this could be extremely
slow or fail.
--
I agree with you Ed. The package should ensure this. The charm fix is
a band-aid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611082
Title:
Upgrading ceph-osd from Kilo to Mitaka "misses"
I think that the package itself should be responsible for ensuring that
the path is accessible by the version ceph it is installing. The charm
can/should certainly implement a workaround as well though.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
--
You received
19 matches
Mail list logo
