Project

General

Profile

Actions

Bug #55841

closed

cephadm: osd memory autotuning doesn't work with FQDN hosts

Added by Adam King almost 2 years ago. Updated almost 2 years ago.

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

0%

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

Description

If you add a host with cephadm that has an FQDN hostname e.g. "host1.example.com" currently when we set the memory target we set it for "osd/host:host1.example.com". However, by default the crush map uses shortnames (e.g. just "host1" in this case). The FQDN config option isn't picked up by the osds for this reason. WE need to set the option for "osd/host1" in this case either by always using the shortname or trying to grab the name from the crush map.


Related issues 2 (0 open2 closed)

Copied to Orchestrator - Backport #56176: pacific: cephadm: osd memory autotuning doesn't work with FQDN hostsResolvedActions
Copied to Orchestrator - Backport #56177: quincy: cephadm: osd memory autotuning doesn't work with FQDN hostsResolvedAdam KingActions
Actions #1

Updated by Adam King almost 2 years ago

  • Status changed from In Progress to Pending Backport
  • Backport set to quincy, pacific
  • Pull request ID set to 46556
Actions #2

Updated by Backport Bot almost 2 years ago

  • Copied to Backport #56176: pacific: cephadm: osd memory autotuning doesn't work with FQDN hosts added
Actions #3

Updated by Backport Bot almost 2 years ago

  • Copied to Backport #56177: quincy: cephadm: osd memory autotuning doesn't work with FQDN hosts added
Actions #4

Updated by Adam King almost 2 years ago

  • Pull request ID changed from 46556 to 46514
Actions #5

Updated by Adam King almost 2 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF