"ceph osd crush set|reweight-subtree" behavior

Hi, We noticed that if one set an osd crush weight using the command ceph osd crush set $id $weight host=$host it updates the osd weight on $host bucket, but does not update it on the "class" bucket (${host}~hdd or ${host}~ssd), and as a result the old weight is still used until one runs `ceph osd crush reweight-all` or do some other changes that cause the crushmap recalculation. The same behaviour is for `ceph osd crush reweight-subtree <name> <weight>` command. Is it expected behavior or should I report a bug to the tracker? I would consider this is ok if I knew a way how to set a weight for a "class" (xyz~hdd or ~ssd) bucket. When I try to use ${host}~ssd it complains about invalid chars ~ in the bucket name. -- Mykola Golub