Hi @noekmc
The alert saying "Requires Server Restart" for the config properties is expected to be there to help administrators to run the "systemctl restart cloudera-scm-server" on the CM host whenever they change the configs and even post changing the config and restarting the CM server. So, how are you validating that the config has not taken affect?
To confirm this, you can simply login to the CM database and run a select query on the "configs" table to check if the properties are there.
For eg, on my postgresDB,
# sudo -u postgres psql
postgres=# \c scm
scm=# select attr, value, host_id, service_id from configs where attr like 'ldap%';
attr | value | host_id | service_id
--------------+--------+---------+------------
ldap_type | LDAP | |
ldap_bind_pw | abcdef | |
ldap_bind_dn | robin | |
(3 rows)
So even after I have added some random values for LDAP in CM UI, the UI will show ""Requires Server Restart" for the already changed properties.
