Warning at startup: "No registered callback for token renewal task. Renewal cancelled"

[tomdug]

We're seeing the following warning at startup when using a StreamingCredentialProvider (in particular EntraIdCredentialsProvider from redis-py-entraid):

No registered callback for token renewal task. Renewal cancelled

Token renewal seems to work normally, so it looks like a false positive that clutters the logs.

Looking into the implementation, the warning comes from the _renew_token_async method in the TokenManager, where self._listener.on_next is initially None. The EntraIdCredentialsProvider creates a CredentialsListener instance at init, and only later sets on_next via the .on_next() method.

This means the token renewal task may start before the callback is set, causing the warning. This only occurs during startup and appears to resolve itself later, presumably once the callback is registered.

Let me know if you need more information

Thanks!

[vladvildanov]

Thanks for reaching out! On my way on this

[vladvildanov]

@tomdug You're right that potentially the renewal may start before the callback is set, but the way how it currently works it shouldn't:

1. When the ConnectionPool was created by client, it fires an event that triggers callback set on_next(callback).
   https://github.com/redis/redis-py/blob/master/redis/asyncio/client.py#L361

2. When the connection is picked from created pool and performs handshake it calls await cred_provider.get_credentials_async() which triggers renewal process. And at this point we already should have a callback set.
   https://github.com/redis/redis-py/blob/master/redis/asyncio/connection.py#L369

Would you be able to provide more information? Do you see the way it could be started before callback was set?