Project

General

Profile

Bug #39980

error from replay does not stored in rbd-mirror status

Added by Mykola Golub 4 months ago. Updated about 1 month ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Target version:
-
Start date:
05/20/2019
Due date:
% Done:

0%

Source:
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

When a remote journal replay completes with an error, `ImageReplayer::handle_replay_complete` properly updates the status by calling `set_state_description` but after this it calls `on_replay_interrupted`, which will call `set_state_description` again and overwrite the error with 0 code.


Related issues

Copied to rbd - Backport #41284: mimic: error from replay does not stored in rbd-mirror status In Progress
Copied to rbd - Backport #41285: luminous: error from replay does not stored in rbd-mirror status In Progress
Copied to rbd - Backport #41286: nautilus: error from replay does not stored in rbd-mirror status In Progress

History

#1 Updated by Mykola Golub 4 months ago

  • Status changed from In Progress to Need Review
  • Pull request ID set to 28179

#2 Updated by Mykola Golub about 1 month ago

  • Status changed from Need Review to Pending Backport

#3 Updated by Nathan Cutler about 1 month ago

  • Copied to Backport #41284: mimic: error from replay does not stored in rbd-mirror status added

#4 Updated by Nathan Cutler about 1 month ago

  • Copied to Backport #41285: luminous: error from replay does not stored in rbd-mirror status added

#5 Updated by Nathan Cutler about 1 month ago

  • Copied to Backport #41286: nautilus: error from replay does not stored in rbd-mirror status added

Also available in: Atom PDF