Hi David, I updated to the latest 17.2.3 but it’s also not there yet. Kind regards, Kenneth On 4 Aug 2022, at 15:59, David Orman <ormandj@xxxxxxxxxxxx<mailto:ormandj@xxxxxxxxxxxx>> wrote: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fceph%2Fceph%2Fpull%2F46480&data=05%7C01%7CKenneth.Waegeman%40ugent.be%7C16f8430a423c4e17b03808da7621d5a2%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637952184940495406%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a3tgPZ2JUA3lu0rtykefkNca7aM4LaLJ3F%2B1%2BuWV2qw%3D&reserved=0 - you can see the backports/dates there. Perhaps it isn't in the version you're running? On Thu, Aug 4, 2022 at 7:51 AM Kenneth Waegeman <Kenneth.Waegeman@xxxxxxxx<mailto:Kenneth.Waegeman@xxxxxxxx>> wrote: Hi all, I’m trying to deploy this spec: spec: data_devices: model: Dell Ent NVMe AGN MU U.2 6.4TB rotational: 0 encrypted: true osds_per_device: 4 crush_device_class: nvme placement: host_pattern: 'ceph30[1-3]' service_id: nvme_22_drive_group service_type: osd But it fails: ceph orch apply -i /etc/ceph/orch_osd.yaml --dry-run Error EINVAL: Failed to validate OSD spec "nvme_22_drive_group": Feature `crush_device_class` is not supported It’s in the docs https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.ceph.com%2Fen%2Fquincy%2Fcephadm%2Fservices%2Fosd%2F%23ceph.deployment.drive_group.DriveGroupSpec.crush_device_class&data=05%7C01%7CKenneth.Waegeman%40ugent.be<http://40ugent.be/>%7C16f8430a423c4e17b03808da7621d5a2%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C637952184940495406%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0MAviN4wXHGQFNLDnInC4%2BwCoowBkpctGBqdYgvdcOQ%3D&reserved=0, and it’s also even in the docs of Pacific. I’m running Quincy 17.2.0 Is this option missing somehow? Thanks!! Kenneth _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx<mailto:ceph-users@xxxxxxx> To unsubscribe send an email to ceph-users-leave@xxxxxxx<mailto:ceph-users-leave@xxxxxxx> _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx<mailto:ceph-users@xxxxxxx> To unsubscribe send an email to ceph-users-leave@xxxxxxx<mailto:ceph-users-leave@xxxxxxx> _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |