Bug #3803
closedrados parsing error with hostnames in mon_host
0%
Description
In /etc/ceph/ceph.conf, if I set hostnames in the mon_host variable and separate them with spaces, the parsing algorithm breaks down. The expectation is that all three of these cases should work. Once hostnames are introduced in the mon_host line, spaces are no longer allowed anywhere or parse errors happen.
Precise is being used, here is the ceph-common package information:
ubuntu@ip-10-151-64-32:~$ apt-cache policy ceph-common
ceph-common:
Installed: 0.48.2-0ubuntu2~cloud0
Candidate: 0.48.2-0ubuntu2~cloud0
Version table:
*** 0.48.2-0ubuntu2~cloud0 0
500 http://ppa.launchpad.net/ubuntu-cloud-archive/grizzly-staging/ubuntu
/ precise/main amd64 Packages
100 /var/lib/dpkg/status
0.41-1ubuntu2.1 0
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise-updates/main
amd64 Packages
0.41-1ubuntu2 0
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise/main amd64 P
ackages
Using IP addresses, spaces as separators:
$ grep mon /etc/ceph/ceph.conf
mon host = 10.151.12.34:6789 10.245.205.215:6789 10.243.34.22:6789
$ rados --id glance lspools
data
metadata
rbd
images
cinder
Using hostnames, spaces as separators (BUG)
$ grep mon /etc/ceph/ceph.conf
mon host = ip-10-151-12-34.ec2.internal:6789 ip-10-245-205-215.ec2.internal:6789 ip-10-243-34-22.ec2.internal:6789
$ rados --id glance lspools
server name not found: ip-10-151-12-34.ec2.internal:6789 ip-10-245-205-215.ec2.internal:6789 ip-10-243-34-22.ec2.internal:6789 (Name or service not known)
unable to parse addrs in 'ip-10-151-12-34.ec2.internal:6789 ip-10-245-205-215.ec2.internal:6789 ip-10-243-34-22.ec2.internal:6789'
couldn't connect to cluster! error -22
Using hostnames, commas as separators
$ grep mon /etc/ceph/ceph.conf
mon host = ip-10-151-12-34.ec2.internal:6789,ip-10-245-205-215.ec2.internal:6789,ip-10-243-34-22.ec2.internal:6789
$ rados --id glance lspools
data
metadata
rbd
images
cinder
Updated by Sage Weil over 11 years ago
Responed to the upstraem bug. This is fixed in master and bobtail, but not backported to argonaut. Should we?
Updated by Sage Weil over 11 years ago
- Status changed from New to Resolved
nevermind.. this is fixed in v0.48.3argonaut too.