Downtime and renaming of a service

Hi,

Currently, if a service which is in a downtime period is renamed, cancelling the downtime doesn’t work. It requires the engine to be restarted, a simple reload isn’t sufficient. In addition, after the restart, the downtime, while effectively cancelled, is still shown as “Nerver started” in the downtime list.

Is it something that one can expect to be fixed? If it can’t be handled as if the service hasn’t been renamed, could it be possible that a simple reload does the job? Because restarting the engine on a poller with thousands of service isn’t something which is absolutely transparent: it takes a couple of minutes and the poller may appear as not running for a little while and services as being in a unknown state.

As a service has an ID, changing its description (ie: name) shouldn’t have an impact on downtimes.

If it can’t be fixed because it would require too much modification of the code, would it be possible to prevent the renaming with a message telling that the service can’t be renamed while in downtime?