When we decrease the number of replicas on the Backup, Volume, or Scheduler services there a "service" DB row will be left behind and it will appear as down, which could mislead sysadmins into believing there is something wrong when there's not.

The operator should wait until the specific service pod has been removed and clean up the database entry.  There is a cinder-manage command to do this (`cinder service remove`)