Project

General

Profile

Actions

Bug #49661

closed

mgr now includes mon metadata as part of osd metadata

Added by Kefu Chai about 3 years ago. Updated about 3 years ago.

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

0%

Source:
Tags:
Backport:
pacific, octopus, nautilus
Regression:
Yes
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Related issues 4 (0 open4 closed)

Related to mgr - Bug #48905: mgr should update mon metadata when mon map is updatedResolvedKefu Chai

Actions
Copied to mgr - Backport #49705: nautilus: mgr now includes mon metadata as part of osd metadataResolvedKefu ChaiActions
Copied to mgr - Backport #49706: octopus: mgr now includes mon metadata as part of osd metadataResolvedKonstantin ShalyginActions
Copied to mgr - Backport #49707: pacific: mgr now includes mon metadata as part of osd metadataResolvedKefu ChaiActions
Actions #1

Updated by Kefu Chai about 3 years ago

  • Related to Bug #48905: mgr should update mon metadata when mon map is updated added
Actions #2

Updated by Kefu Chai about 3 years ago

  • Status changed from New to Fix Under Review
  • Assignee set to Kefu Chai
  • Regression changed from No to Yes
  • Pull request ID set to 39937
Actions #3

Updated by Kefu Chai about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49705: nautilus: mgr now includes mon metadata as part of osd metadata added
Actions #5

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49706: octopus: mgr now includes mon metadata as part of osd metadata added
Actions #6

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49707: pacific: mgr now includes mon metadata as part of osd metadata added
Actions #7

Updated by Ernesto Puerta about 3 years ago

  • Priority changed from Normal to High
  • Severity changed from 3 - minor to 2 - major
Actions #8

Updated by Loïc Dachary about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF