Project

General

Profile

Bug #50957

batch --report shows incorrect % of device when using --block-db-size

Added by Andrew Schoen 2 months ago. Updated about 2 months ago.

Status:
Pending Backport
Priority:
Low
Assignee:
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
nautilus octopus pacific
Regression:
No
Severity:
4 - irritation
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The % of device calculation always shows as 100%, even if --block-db-size
is given with a smaller value than the total size of the device.

[root@ceph-aschoen cephuser]# ceph-volume lvm batch --bluestore /dev/vdd --db-devices /dev/vdg --report
--> passed data devices: 1 physical, 0 LVM
--> relative data size: 1.0
--> passed block_db devices: 1 physical, 0 LVM

Total OSDs: 1

Type            Path                                                    LV Size         % of device
----------------------------------------------------------------------------------------------------
data /dev/vdd 15.00 GB 100.00%
block_db /dev/vdg 15.00 GB 100.00%

[root@ceph-aschoen cephuser]# ceph-volume lvm batch --bluestore /dev/vdd --db-devices /dev/vdg --block-db-size 5368709120 --report
--> passed data devices: 1 physical, 0 LVM
--> relative data size: 1.0
--> passed block_db devices: 1 physical, 0 LVM

Total OSDs: 1

Type            Path                                                    LV Size         % of device
----------------------------------------------------------------------------------------------------
data /dev/vdd 15.00 GB 100.00%
block_db /dev/vdg 5.00 GB 100.00%

Related issues

Copied to ceph-volume - Backport #51106: octopus: batch --report shows incorrect % of device when using --block-db-size In Progress
Copied to ceph-volume - Backport #51107: nautilus: batch --report shows incorrect % of device when using --block-db-size Resolved
Copied to ceph-volume - Backport #51108: pacific: batch --report shows incorrect % of device when using --block-db-size In Progress

History

#1 Updated by Konstantin Shalygin 2 months ago

  • Priority changed from Normal to Low
  • Source set to Community (user)
  • Backport set to nautilus octopus pacific
  • Severity changed from 3 - minor to 4 - irritation

#2 Updated by Kefu Chai about 2 months ago

  • Status changed from New to Pending Backport
  • Pull request ID set to 41506

#3 Updated by Backport Bot about 2 months ago

  • Copied to Backport #51106: octopus: batch --report shows incorrect % of device when using --block-db-size added

#4 Updated by Backport Bot about 2 months ago

  • Copied to Backport #51107: nautilus: batch --report shows incorrect % of device when using --block-db-size added

#5 Updated by Backport Bot about 2 months ago

  • Copied to Backport #51108: pacific: batch --report shows incorrect % of device when using --block-db-size added

Also available in: Atom PDF