ceph with mitaka UCA does not deploy ceph mon

[Matthew Mosesohn]

9.0 Custom ISO 371 can be used to reproduce this, but comment out ceph APT pins in setup_repositories.pp

 2016-01-29 14:57:50 +0000 /Stage[main]/Ceph::Mon/Exec[Wait for Ceph quorum] (err): Failed to call refresh: ceph mon stat | g
rep -q 'quorum.*node-1' returned 1 instead of one of [0]
2016-01-29 14:57:50 +0000 /Stage[main]/Ceph::Mon/Exec[Wait for Ceph quorum] (err): ceph mon stat | grep -q 'quorum.*node-1'
returned 1 instead of one of [0]

root@node-1:/var/log# ceph mon stat
2016-01-29 15:25:41.941956 7f30c0226700 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory
2016-01-29 15:25:41.942873 7f30c0226700 -1 monclient(hunting): ERROR: missing keyring, cannot use cephx for authentication
2016-01-29 15:25:41.944166 7f30c0226700 0 librados: client.admin initialization error (2) No such file or directory
Error connecting to cluster: ObjectNotFound

Diagnostic snapshot attached

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Matthew Mosesohn (raytrac3r)]

Nastya, I would like to suggest removing this tag. This is a very low priority bug because if you use MOS built Ceph packages, deployment is fine. This bug only concerns using upstream Ubuntu UCA ceph packages.

[Nastya Urlapova (aurlapova)]

@Matt it is up to you, if you aren't going run full set of tests against UCA packages, I may remove tag.

[Sam Stoelinga (sammiestoel)]

I am not using UCA packages on 9.0 but looks like I'm still hitting the same issue. See logs: http://paste.openstack.org/show/564331/

Steps to reproduce:
1. Use a network template to separate ceph/public from management network
2. Deploy an environment with 1 controller and 2 compute + ceph-osd combined.

[Sam Stoelinga (sammiestoel)]

Additionallity this message is seen in ceph-mon log:
0 mon.node-10 does not exist in monmap, will attempt to join an existing cluster
-1 /usr/bin/ceph-mon: error generating initial monmap: (2) No such file or directory

[Sam Stoelinga (sammiestoel)]

My issue was unrelated to this bug. The issue was that ceph/public network role did not have an assigned ip address on the controller nodes. This was caused because I re-uploaded a network template on a failed env which did not update ceph/public network role IP addresses.