Project

General

Profile

Bug #49102

Windows RBD service issues

Added by Lucian Petrut 24 days ago. Updated 9 days ago.

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

0%

Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

This [1] PR fixes a few issues affecting the newly introduced Windows RBD service:

  • New rbd mappings are now started by the ceph service, thus no longer being tied to the user session
  • Fixed the block count overflow for image larger than 2TB
  • Added a “--non-persistent” map option
  • Limited the scope of the commands executed by the Ceph service
  • Added configurable service start and image map timeouts. Also fixed an issue where the service would hang indefinitely when failing to remap images
  • Changed the way in which the service handles remap failures. Previously, it was getting marked as stopped but already started daemons kept running. Now, by default, the service will keep running unless the “--remap-failure-fatal” option is set, in which case it will cleanup existing mappings before shutting down.
  • Fixed a few error propagation issues

[1] https://github.com/ceph/ceph/pull/39224

Those changes will have to be backported to Pacific.


Related issues

Copied to Ceph - Backport #49155: pacific: Windows RBD service issues Resolved

History

#1 Updated by Jan Fajerski 24 days ago

  • Status changed from New to Fix Under Review
  • Backport set to pacific

#2 Updated by Jason Dillaman 22 days ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Backport Bot 22 days ago

#4 Updated by Nathan Cutler 9 days 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".

Also available in: Atom PDF