So the problem was an issue with trying to use "master" branch of ceph-ansible, instead of a tagged branch... From: Sebastien Han [mailto:shan@xxxxxxxxxx] Sent: Friday, February 01, 2019 9:40 AM To: Will Dennis Cc: ceph-ansible@xxxxxxxxxxxxxx Subject: Re: [Ceph-ansible] Problem with "ceph-mon : waiting for the monitor(s) to form the quorum" play Are you trying to deploy mimic or luminous with latest ceph-master master? If so, then your failure is expected. use stable-3.2 to deploy L or M, current master works only with Nautilus (not released yet). Thanks! --------- Sébastien Han Principal Software Engineer, Storage Architect Sorry for the bother. -----Original Message----- From: ceph-users [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] On Behalf Of Will Dennis Sent: Friday, February 01, 2019 10:02 AM To: ceph-users@xxxxxxxxxxxxxx Subject: Correct syntax for "mon host" line in ceph.conf? I am using the "ceph-ansible" set of Ansible playbooks to try to get a test cluster up and running (in Vagrant.) I am deploying Mimic (13.2.4) on Ubuntu 16.04, with one (for now) monitor, and three osd servers. I have a play in the Ansible that is erroring out, and in troubleshooting what that play does manually, I see: vagrant@mon0:~$ sudo ceph --cluster ceph -n mon. -k /var/lib/ceph/mon/ceph-mon0/keyring mon_status --format json server name not found: [v2:192.168.42.10:3300 (Name or service not known) unable to parse addrs in '[v2:192.168.42.10:3300,v1:192.168.42.10:6789]' 2019-02-01 04:26:52.446 7f8a66e0e700 -1 monclient: get_monmap_and_config cannot identify monitors to contact [errno 22] error connecting to the cluster The /etc/ceph/ceph.conf file on mon0 has: vagrant@mon0:~$ less /etc/ceph/ceph.conf # Please do not change this file directly since it is managed by Ansible and will be overwritten [global] mon initial members = mon0 fsid = 039e920d-5f75-4fa3-aee1-f5a90b073f9e mon host = [v2:192.168.42.10:3300,v1:192.168.42.10:6789] public network = 192.168.42.0/24 cluster network = 192.168.42.0/24 If I change the "mon host" line to: mon host = 192.168.42.10 Then the "mon_status" command works: vagrant@mon0:~$ sudo ceph --cluster ceph -n mon. -k /var/lib/ceph/mon/ceph-mon0/keyring mon_status --format json {"name":"mon0","rank":0,"state":"leader","election_epoch":5,"quorum":[0],"features":{"required_con":"144115738102218752","required_mon":["kraken","luminous","mimic","osdmap-prune"],"quorum_con":"4611087854031142907","quorum_mon":["kraken","luminous","mimic","osdmap-prune"]},"outside_quorum":[],"extra_probe_peers":[],"sync_provider":[],"monmap":{"epoch":1,"fsid":"839b40b9-4260-485d-ad74-4c4fbb223689","modified":"0.000000","created":"0.000000","features":{"persistent":["kraken","luminous","mimic","osdmap-prune"],"optional":[]},"mons":[{"rank":0,"name":"mon0","addr":"192.168.42.10:6789/0","public_addr":"192.168.42.10:6789/0"}]},"feature_map":{"mon":[{"features":"0x3ffddff8ffa4fffb","release":"luminous","num":1}],"client":[{"features":"0x3ffddff8ffa4fffb","release":"luminous","num":1}]}} So, my question is: is the syntax of the "mon host" line that ceph-ansible is generating correct? _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |