Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
python-0.3.4
-
None
Description
Starting a server w/authentication, then connecting to it via a python thin client w/an incorrect username and password.
The message/stacktrace is ambiguous leading clients to believe that they've connected, and something is amiss w/the server.
client = Client(username='incorrect-user-name', password='incorrect-password', use_ssl=False) client.connect('127.0.0.1', 10800) #client(nodes) print("connected to: ".format(client)) print("cache names: ".format(client.get_cache_names))
the stacktrace is :
connected to: Traceback (most recent call last): cache names: File "C:/dev/python-thin-client/examples/get_and_put.py", line 30, in <module> print(client.get_cache_names()) File "C:\dev\python-thin-client\pyignite\utils.py", line 249, in ste_wrapper result = fn(*args, **kwargs) File "C:\dev\python-thin-client\pyignite\client.py", line 521, in get_cache_names return cache_get_names(self.random_node) File "C:\dev\python-thin-client\pyignite\utils.py", line 273, in wrapper return func(obj, *args, **kwargs) File "C:\dev\python-thin-client\pyignite\client.py", line 222, in random_node raise ReconnectError('Can not reconnect: out of nodes.') from None pyignite.exceptions.ReconnectError: Can not reconnect: out of nodes.
ReconnectError: Can not reconnect: out of nodes exception: allows the user to make the conclusion that the connection is successful, but something is wrong with the server.
Attachments
Issue Links
- is fixed by
-
IGNITE-14240 Handle authentication error on python thin client properly
- Resolved