Project

General

Profile

Actions

Bug #6706

closed

radosgw init script and hostname variations

Added by David Moreau Simard over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

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

Description

Relevant snippet:

# mapped to this host?
host=`ceph-conf -n $name host`
if [ "$host" != `hostname` ]; then
    continue
fi

Depending on how a server is configured, the output of "hostname" can be different.
Given a hostname "test.example.org", sometimes it'll output "test" - other times it will output "test.example.org".

This can be confusing for the user relative to the configuration that is expected in ceph.conf.
Should the "host" value be the complete fqdn ("hostname -f") or the hostname ("hostname -s") ?

Relevant snippet:

[client.radosgw.gateway]
  # Need this parameter for the default apache2 packages
  rgw print continue = false

  rgw enable usage log = true
  rgw enable ops log = true
  rgw usage log tick interval = 30
  rgw usage log flush threshold = 1024
  host = rgw01      # <---------
  keyring = /var/lib/ceph/radosgw/keyring.rgw
  rgw socket path = /tmp/radosgw.sock
  log file = /var/log/ceph/radosgw.log

I propose that we maintain compatibility with the existing init script but be a bit more permissive by allowing both the fqdn (hostname -f) and the hostname (hostname -s).


Related issues 1 (0 open1 closed)

Has duplicate rgw - Bug #6694: radosgw upstart script doesn't provide the -n parameterDuplicate10/31/2013

Actions
Actions #1

Updated by Sage Weil over 10 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF