nova-manage api_db sync - NotSupportedWarning ['use_tpool']

[Corey Bryant]

In the nova queens 17.0.0.0b3 release, I'm seeing the following:

$ nova-manage api_db sync
/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py:332: NotSupportedWarning: Configuration option(s) ['use_tpool'] not supported
  exception.NotSupportedWarning

This is with Ubuntu packages, so I've not tried to recreate with pip-installed packages.

In our /etc/nova/nova.conf use_tpool is commented out.

If I revert the following commit, the error goes away: https://github.com/openstack/nova/commit/910008e2ef5dae1698ff7db791f4816c728c8bd0

[Corey Bryant (corey.bryant)]

Worth noting I tested with both oslo.db 4.31.0 4.33.0.

[Matt Riedemann (mriedem)]

I've been seeing this too but don't really know how to resolve it.

[Surya Seetharaman (tssurya)]

IMO, this patch in oslo_db should fix this issue - https://github.com/openstack/oslo.db/commit/c432d9e93884d6962592f6d19aaec3f8f66ac3a2

[Tetsuro Nakamura (tetsuro0907)]

We've also been seeing this.

@tssurya I don't fully understand your patch, but why is this status "Won't Fix"? Should we report this bug in oslo project?

[Surya Seetharaman (tssurya)]

@tetsuro0907 : Apologies for not being very clear in my previous comment. What I meant to say was this issue originates from oslo_db, it is not exactly a nova-manage issue. There was already a bug opened in oslo.db (https://bugs.launchpad.net/oslo.db/+bug/1549915) for which stephenfin has already proposed a fix (https://review.openstack.org/#/c/551256/) which got merged in oslo.db versions > 4.34.0. So using oslo.db versions less than 4.34 will cause this warning. However since its only a warning and see discussion here:http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-04-18.log.html#t2018-04-18T19:09:34 it was decided to mark this as a won't fix.

[Surya Seetharaman (tssurya)]

If its very annoying one of the ways I see is to ignore this in nova-manage : https://review.openstack.org/#/c/568785/ . However IMHO, since this is not needed in master, and since this is not a clean way of doing it, I would not want to do this.