Actions
Bug #10777
openceph-deploy task doesnot create osd as per ctx.cluster.remotes
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
Have observerd while creating ceph cluster using ceph-deploy task,
the way osds are associated in ctx.cluster.remotes and the way actually osd are created in cluster are different.
Eg:
As par ctx.cluster.remotes:
2015-02-06 11:18:44,142.142 INFO:teuthology.task.internal:roles: ubuntu@ip-10-15-16-34 - ['mon.a', 'osd.0', 'osd.1', 'osd.2'] 2015-02-06 11:18:44,142.142 INFO:teuthology.task.internal:roles: ubuntu@ip-10-15-16-35 - ['mon.b', 'osd.3', 'osd.4'] 2015-02-06 11:18:44,142.142 INFO:teuthology.task.internal:roles: ubuntu@ip-10-15-16-36 - ['mon.c', 'osd.5', 'client.0'] 2015-02-06 11:18:44,142.142 INFO:teuthology.run_tasks:Running task internal.check_conflict...
As par ceph osd tree command:
# id weight type name up/down reweight -1 1.14 root default -2 0.38 host ip-10-15-16-35 0 0.19 osd.0 up 1 1 0.19 osd.1 up 1 -3 0.57 host ip-10-15-16-34 2 0.19 osd.2 up 1 3 0.19 osd.3 up 1 4 0.19 osd.4 up 1 -4 0.19 host ip-10-15-16-36 5 0.19 osd.5 up 1
Updated by Zack Cerza about 9 years ago
- Priority changed from High to Low
This does look like a bug, but it's not really problematic for us. I'd be happy to review patches, but can't justify dedicating resources to fixing it on our end.
Updated by Dan Mick over 8 years ago
- Assignee set to Dan Mick
- Regression set to No
Updated by Dan Mick over 8 years ago
- Subject changed from ceph-deploy task doesnot create osd as par ctx.cluster.remotes to ceph-deploy task doesnot create osd as per ctx.cluster.remotes
Updated by Dan Mick over 8 years ago
Need to investigate this; it doesn't seem like it could be true.
Actions