Description of problem: On restarting the nova_scheduelr container after fresh install, it goes starts and goes into healthy status, however docker logs shows the following exception INFO:__main__:Setting permission for /var/log/nova/nova-api-metadata.log.5.gz INFO:__main__:Setting permission for /var/log/nova/nova-api.log.10.gz ++ cat /run_command + CMD='/usr/bin/nova-scheduler ' + ARGS= + [[ ! -n '' ]] + . kolla_extend_start ++ [[ ! -d /var/log/kolla/nova ]] +++ stat -c %a /var/log/kolla/nova ++ [[ 2755 != \7\5\5 ]] ++ chmod 755 /var/log/kolla/nova ++ . /usr/local/bin/kolla_nova_extend_start + echo 'Running command: '\''/usr/bin/nova-scheduler '\''' + exec /usr/bin/nova-scheduler Running command: '/usr/bin/nova-scheduler ' /usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py:332: NotSupportedWarning: Configuration option(s) ['use_tpool'] not supported exception.NotSupportedWarning Version-Release number of selected component (if applicable): 13 How reproducible: 100% Steps to Reproduce: 1. Restart nova_scheduler 2. Use docker_logs to observe logs when starting 3. Actual results: Exceptions in logs Expected results: No exceptions Additional info:
Can you provide the nova scheduler logs for this.
This was resolved in OSP 14 but I guess we need the backport, which is in progress upstream. However, despite appearances, this is not an exception: it's just a warning that has been defined in the 'oslo_db.exception' module for some unknown reason. As such, I don't think this is an issue and the warning can be safely ignored.