Bug #57191
closed[cephadm] os tuned profile setting names are not validated from cephadm side
0%
Description
By setting wrong setting name which is not exist in sysctl option,
still cephadm tuned-profile apply command executed successfully
It should throw an error for the wrong setting name.
Tested in
ceph version 17.0.0-14295-g042ca579 (042ca579c2e4fece1853503d982b6afc0a0478dc) quincy (dev)
[ceph: root@magna086 /]# cat test-os-profile.yaml
profile_name: test-os-profile
placement:
hosts:
- magna086
- magna087
settings:
fs.file-max: 1000000
vm.swappiness: '30'
fs.aio-max-nr: 1048576
kernel.threads-max: 35511
wrong.dummy: 100
[ceph: root@magna086 /]# ceph orch tuned-profile apply -i test-os-profile.yaml
Saved tuned profile test-os-profile
wrong.dummy is not a valid os setting-name but ceph orch saved that profile.
Updated by Redouane Kachach Elhichou over 1 year ago
- Status changed from New to In Progress
- Assignee set to Redouane Kachach Elhichou
Updated by Adam King over 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 47787
Updated by Adam King over 1 year ago
this is now being covered as part of https://tracker.ceph.com/issues/57192 and is fixed in main and awaiting quincy backport
Updated by Adam King over 1 year ago
- Status changed from Fix Under Review to Resolved