https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2013-10-31T16:59:55ZCeph devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=291362013-10-31T16:59:55ZTamilarasi muthamizhantamil.muthamizhan@inktank.com
<ul></ul><pre>
ubuntu@mira025:~/ceph-dep/ceph-deploy$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 902G 5.7G 850G 1% /
udev 7.8G 12K 7.8G 1% /dev
tmpfs 3.2G 336K 3.2G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 7.9G 0 7.9G 0% /run/shm
cgroup 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sdb1 931G 43M 931G 1% /var/lib/ceph/osd/ceph-0
/dev/sdc1 931G 33M 931G 1% /var/lib/ceph/osd/ceph-3
ubuntu@mira025:~/ceph-dep/ceph-deploy$ sudo ceph osd tree
# id weight type name up/down reweight
-1 2.73 root default
-2 0.91 host mira025
0 0.91 osd.0 down 1
-3 1.82 host mira038
1 0.91 osd.1 down 1
2 0.91 osd.2 down 1
3 0 osd.3 down 0
4 0 osd.4 down 0
ubuntu@mira025:~/ceph-dep/ceph-deploy$ sudo ceph -v
ceph version 0.72-rc1-83-g592a99c (592a99ccd8da2d7843ebb7ce6439566732580b7a)
</pre> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=291582013-11-01T16:44:24ZSage Weilsage@newdream.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fix Under Review</i></li></ul> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=291592013-11-01T16:52:14ZSage Weilsage@newdream.net
<ul><li><strong>Assignee</strong> deleted (<del><i>Alfredo Deza</i></del>)</li></ul> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=292012013-11-04T18:37:32ZSage Weilsage@newdream.net
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Resolved</i></li></ul> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=294052013-11-13T19:03:39ZTamilarasi muthamizhantamil.muthamizhan@inktank.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>In Progress</i></li></ul><p>this bug was caused by crush lookup failure.</p>
<p>I see similar issue with one of my local clusters: mira047 and mira048.</p> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=296832013-11-22T10:53:13ZIan Colleicolle@redhat.com
<ul><li><strong>Subject</strong> changed from <i>ceph-deploy: new osds added to the cluster is not starting up </i> to <i>new osds added to the cluster not starting up due to crush lookup failure</i></li><li><strong>Category</strong> deleted (<del><i>ceph-deploy</i></del>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>12</i></li><li><strong>Assignee</strong> set to <i>Dan Mick</i></li></ul> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=300082013-12-03T19:02:43ZDan Mickdmick@redhat.com
<ul><li><strong>Status</strong> changed from <i>12</i> to <i>Need More Info</i></li></ul><p>I guess I'm not sure what the expected behavior is here; do we think that the OSDs should start, but not do much, until they're added to the crush map?</p> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=300212013-12-04T15:52:15ZDan Mickdmick@redhat.com
<ul></ul><p>Sage suspects this may have been fixed by 1bb5aadbca80eb46d5393bb1ad68af3da025e157</p> devops - Bug #6698: new osds added to the cluster not starting up due to crush lookup failurehttps://tracker.ceph.com/issues/6698?journal_id=300232013-12-04T17:08:52ZTamilarasi muthamizhantamil.muthamizhan@inktank.com
<ul><li><strong>Status</strong> changed from <i>Need More Info</i> to <i>Resolved</i></li></ul><p>tried reproducing this issue by upgrading from dumpling to emperor and then trying to add osds to the cluster but it worked fine.<br />closing the bug for now.</p>