Ceph » RADOS

workunits/mon/ping.py does test ceph ping mon.{mon_id}, see https://github.com/ceph/ceph/blob/master/qa/workunits/mon/ping.py#L79 and https://github.com/ceph/ceph/blob/master/qa/workunits/mon/ping.py#L96

Huh. So it does. I don't understand how both of these haven't just been failing consistently then.

Ah. It depends on how build_initial_monmap works.

In my case, ping mon.<specific> returns ENOENT, which the CLI shows as Error connecting to cluster: ObjectNotFound.

I have a ceph.conf with mon_initial_members and mon_host set, but no monmap; this causes build_initial_monmap to return a monmap with 'noname-a', 'noname-b', etc. set in it; then, MonClient::ping_monitor tries to find a monitor named 'noname-<specific>', which of course fails and returns ENOENT.

Running with a real monmap file fixes this, as does connecting to the cluster first (because then the monmap is 'real', with real names).

https://github.com/ceph/ceph/pull/12891