rhel-osp-director:   ceph mons don't start after reboot
Environment:
openstack-puppet-modules-9.0.0-0.20160802183056.8c758d6.el7ost.noarch
instack-undercloud-5.0.0-0.20160818065636.41ef775.el7ost.noarch
libcephfs1-10.2.2-38.el7cp.x86_64
ceph-radosgw-10.2.2-38.el7cp.x86_64
ceph-mon-10.2.2-38.el7cp.x86_64
ceph-common-10.2.2-38.el7cp.x86_64
python-cephfs-10.2.2-38.el7cp.x86_64
ceph-selinux-10.2.2-38.el7cp.x86_64
ceph-base-10.2.2-38.el7cp.x86_64
puppet-ceph-2.0.0-0.20160823145734.4e36628.1.el7ost.noarch
ceph-osd-10.2.2-38.el7cp.x86_64

Steps to reproduce:
1.
Deploy overcloud 10 with:
openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --swift-storage-scale 0 --block-storage-scale 0 --neutron-network-type vxlan --neutron-tunnel-types vxlan --ntp-server clock.redhat.com --timeout 90 -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml --ceph-storage-scale 1


network-environment.yaml has the following in it:
parameter_defaults:
  ExtraConfig:
    ceph::conf::args:
      global/osd_max_object_name_len:
        value: 256
      global/osd_max_object_namespace_len:
        value: 64


2. Reboot the overcloud nodes.
3. Check ceph status.

Result:
The ceph monitors are down and as a result, the ceph osd doesn't start on the ceph node.


Expected result:
The ceph monitors should start after reboot.

w/a:
Login to each mon host and run:
systemctl start ceph-mon@<hostname>