Project

General

Profile

Actions

Bug #42335

closed

the progress percent of creating thick-provisoin image exceeds 100%

Added by 鸿洁 杨 over 4 years ago. Updated about 4 years ago.

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

0%

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

Description

!!


Files

123.png (17.7 KB) 123.png bug_info 鸿洁 杨, 10/16/2019 06:04 AM

Related issues 2 (0 open2 closed)

Copied to rbd - Backport #43507: mimic: the progress percent of creating thick-provisoin image exceeds 100%ResolvedNathan CutlerActions
Copied to rbd - Backport #43508: nautilus: the progress percent of creating thick-provisoin image exceeds 100%ResolvedNathan CutlerActions
Actions #1

Updated by 鸿洁 杨 over 4 years ago

I create an 10M thcik-provision image, the progress percent info exceeds 100% in progress, up to 120%, but ends with 100%. Similarly,if create a 3M thcik-provision image,the percent goes up to 133%, ends with 100%

Actions #2

Updated by 鸿洁 杨 over 4 years ago

鸿洁 杨 wrote:

!!I create an 10M thcik-provision image, the progress percent info exceeds 100% in progress, up to 120%, but ends with 100%. Similarly,if create a 3M thcik-provision image,the percent goes up to 133%, ends with 100%

Actions #3

Updated by Mykola Golub over 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 30954
Actions #4

Updated by Jason Dillaman over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus,mimic
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43507: mimic: the progress percent of creating thick-provisoin image exceeds 100% added
Actions #6

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43508: nautilus: the progress percent of creating thick-provisoin image exceeds 100% added
Actions #7

Updated by Nathan Cutler about 4 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