Red Hat Bugzilla – Bug 1304367
overcloud deployment finished successfully and Ceph's OSDs are down
Last modified: 2016-04-26 10:47:47 EDT
Created attachment 1120745 [details]
overcloud deployment log
Description of problem:
The deployment of the overcloud installed 3 Ceph storage nodes, each with 4 hard drives (1 for te OS 3 for the OSDs) was successful, finished with return value of 0.
Though the deployment was a success the OSDs are down. The services didn't start - had to do it manually.
Version-Release number of selected component (if applicable):
(though I know the same happens with OSPD 7.2 and 7.3)
Steps to Reproduce:
1. Add additional hard drives to the would be Ceph storage nodes
2. Set the ceph.yaml file with additional hard drives:
3. Deploy the overcloud
The OSDs are down
[heat-admin@overcloud-controller-0 ~]$ sudo ceph osd tree
ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY
-1 0.59995 root default
-2 0.29997 host overcloud-cephstorage-2
0 0.09999 osd.0 down 0 1.00000
4 0.09999 osd.4 down 0 1.00000
7 0.09999 osd.7 down 0 1.00000
-3 0.29997 host overcloud-cephstorage-1
1 0.09999 osd.1 down 0 1.00000
6 0.09999 osd.6 down 0 1.00000
8 0.09999 osd.8 down 0 1.00000
2 0 osd.2 down 0 1.00000
3 0 osd.3 down 0 1.00000
5 0 osd.5 down 0 1.00000
All the OSDs should be up
Could this be a duplicate of #1298620?
yes, but this is really an equivalent BZ for 1297251 but targeted for OSP8.
There are many BZs with same root cause (udev rules cause OSDs to be down after deployment), one of which is 1309926 and is targeted for OSP8. That BZ is being actively worked, and an external tracker (https://review.openstack.org/276141) is nearly resolved. I think this BZ should be marked as a duplicate of 1309926.
*** Bug 1309926 has been marked as a duplicate of this bug. ***
The deployment finished successfully with the OSDs up and running
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.