Project

General

Profile

Actions

Bug #58465

closed

cephadm: haproxy nfs backends don't properly handle multiple nfs of the same rank

Added by Adam King over 1 year ago. Updated about 1 year ago.

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

0%

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

Description

When the host that an nfs is on goes offline and we deploy a replacement on another host matching the placement. That replacement and the nfs daemon on the offline host will have the same rank. The code to handle getting the IPs for the backend service for the haproxy config doesn't handle this properly and just ends up getting the IP from the node of the nfs of that rank it happens to iterate over last. We should instead always be checking the rank_generated for the nfs daemons and picking the one whose rank_generated is higher.


Related issues 2 (0 open2 closed)

Copied to Orchestrator - Backport #58775: pacific: cephadm: haproxy nfs backends don't properly handle multiple nfs of the same rank ResolvedAdam KingActions
Copied to Orchestrator - Backport #58776: quincy: cephadm: haproxy nfs backends don't properly handle multiple nfs of the same rank ResolvedAdam KingActions
Actions #1

Updated by Adam King about 1 year ago

  • Status changed from In Progress to Pending Backport
  • Pull request ID set to 49754
Actions #2

Updated by Backport Bot about 1 year ago

  • Copied to Backport #58775: pacific: cephadm: haproxy nfs backends don't properly handle multiple nfs of the same rank added
Actions #3

Updated by Backport Bot about 1 year ago

  • Copied to Backport #58776: quincy: cephadm: haproxy nfs backends don't properly handle multiple nfs of the same rank added
Actions #4

Updated by Backport Bot about 1 year ago

  • Tags set to backport_processed
Actions #5

Updated by Adam King about 1 year ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF