Project

General

Profile

Actions

Fix #4953

closed

ceph-deploy: dns mismatches can cause gatherkeys to fail

Added by Anonymous almost 11 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
ceph-deploy
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Our cluster has two networks, a fast network and a control network. The servers names are nodeX for the fast network and nodeX-control for the control network.
Using ceph-deploy to setup a cluster, I issued the following commands.

ceph-deploy new node1-control node2-control node3-control
ceph-deploy mon create
ceph-deploy gatherkeys

the gatherkeys step fails. In looking in /var/run/ceph, the asok files were created with the nodeX name and not the specified nodeX-control.

Upon advice from Sage, I reran this, specifying hosts using the format logicalname:dns name, so the first command turned into this:

ceph-deploy new node1:node1-control node2:node2-control node3:node3-control

This allowed the following steps to complete and the ceph.conf file showed the correct IP addresses (from the control IP block).

It seems like the ceph-deploy process could error out if there is confusion when resolving the hostnames into IP addresses, such as in our case where the name and IP address did not match.

Actions #1

Updated by Tamilarasi muthamizhan almost 11 years ago

  • Project changed from CephFS to devops
  • Category set to ceph-deploy
Actions #2

Updated by Alfredo Deza over 10 years ago

  • Status changed from New to Resolved

ceph-deploy will now check for common errors (like the one mentioned) when deploying monitors.

Actions

Also available in: Atom PDF