Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Moving this bug to verified state. Command console output: [ubuntu@host031 ~]$ sudo osdmaptool --test-map-pgs --pg-num 64 ./osdmap osdmaptool: osdmap file './osdmap' pool 1 pg_num 64 pool 2 pg_num 64 #osd count first primary c wt wt osd.0 42 12 12 0.904388 1 osd.1 51 12 12 0.904388 1 osd.2 40 15 15 0.904388 1 osd.3 51 14 14 0.904388 1 osd.4 42 15 15 0.904388 1 osd.5 40 13 13 0.904388 1 osd.6 35 15 15 0.904388 1 osd.7 46 21 21 0.904388 1 osd.8 37 11 11 0.904388 1 in 9 avg 42 stddev 5.37484 (0.127972x) (expected 6.1584 0.146629x)) min osd.6 35 max osd.1 51 size 0 0 size 1 0 size 2 0 size 3 128
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3387