DescriptionMichael J. Kidd
2019-10-29 17:10:06 UTC
Description of problem:
Attempted to weight up a newly added osd node using:
# ceph osd reweight-subtree hostname 3.943
No peering or data movement occurred
Version-Release number of selected component (if applicable):
RHCS 3.3
How reproducible:
Every time
Steps to Reproduce:
1. Use reweight-subtree command
Actual results:
- no peering or data movement triggered
Expected results:
- peering / data movement
Additional info:
- Cluster had upmap entries, but it's unclear if upmap entries are a contributing factor
Correction,
The command issued was:
# ceph osd crush reweight-subtree hostname 3.943
I had a typo in my initial submission.
Note that the subtree items were reweighted according to 'ceph osd tree', however they never had PGs assigned to them as confirmed by no peering/recovery IO, also 'ceph osd df tree' showed 0 PGs per OSD on the reweighted OSDs.
Thanks!
Comment 9Jane smith
2020-11-04 09:54:44 UTC
Comment hidden (spam)
This comment was flagged a spam, view the edit history to see the original text if required.
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 (Important: Red Hat Ceph Storage 4.2 Security and Bug Fix Update), 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/RHSA-2021:2445