no keeper selected error on python client

[EnekoGonzalez3]

After deploying the system locally with the local deployment script, if i run the Python Client Test, it shows the following log and errors:

[ChronoLog] eneko@eneko-IIT:~/Documents/Repositories/ChronoLog/python_client$ LD_LIBRARY_PATH=/home/eneko/chronolog/Debug/lib:$LD_LIBRARY_PATH python3 test.py
Basic test for py_chronolog_client
Attempt to acquire story without ChronoVisor connection returns : (-15, None)
client.Connect() call returns: 0
clientCreateCronicle() returned 0
[4200.443728] mercury->fatal: [error] /tmp/eneko/spack-stage/spack-stage-mercury-2.2.0-a4hgdtnahcrdsfglsnhhj7b2muojjtg2/spack-src/src/na/na_ofi.c:5556
na_ofi_addr_lookup(): Unrecognized provider type found from: ://127.0.0.1:6666
Function returned HG_INVALID_ARG
[4200.451280] mercury->fatal: [error] /tmp/eneko/spack-stage/spack-stage-mercury-2.2.0-a4hgdtnahcrdsfglsnhhj7b2muojjtg2/spack-src/src/na/na_ofi.c:5556
na_ofi_addr_lookup(): Unrecognized provider type found from: ://127.0.0.1:6668
Function returned HG_INVALID_ARG
[4200.451313] mercury->fatal: [error] /tmp/eneko/spack-stage/spack-stage-mercury-2.2.0-a4hgdtnahcrdsfglsnhhj7b2muojjtg2/spack-src/src/na/na_ofi.c:5556
na_ofi_addr_lookup(): Unrecognized provider type found from: ://127.0.0.1:6670
Function returned HG_INVALID_ARG
client.AcquireStory() returned: (0, <py_chronolog_client.StoryHandle object at 0x753da34116f0>)
Aquired Story = my_story within chronicle = py_chronicle
logging 4 events for my_story using the StoryHandle
client.ReleaseStory() returned: 0
client.Disconnect() returned: 0

Also this is the client log:

eneko@eneko-IIT:~/chronolog/Debug/bin$ cat /tmp/chrono_client.log
[2025-01-21 13:47:56.791] [chrono_client] [info] [ChronologClientImpl] Client Identity - Login: eneko, EUID: 1000, HostID: 1757367822, PID: 9577
[2025-01-21 13:47:57.119] [chrono_client] [error] [ChronoLogClientImpl] Failed to acquire story 'my_story' from chronicle 'py_chronicle': Client is not connected or is shutting down.
[2025-01-21 13:47:57.119] [chrono_client] [info] [RpcVisorClient] Connection successful for Account=1000, HostID=1757367822, PID=9577
[2025-01-21 13:47:57.119] [chrono_client] [info] [RPCVisorClient] Initiating creation of chronicle: Name=py_chronicle, Flags=1
[2025-01-21 13:47:57.120] [chrono_client] [info] [RPCVisorClient] Successfully created chronicle with Name=py_chronicle, Flags=1
[2025-01-21 13:47:57.120] [chrono_client] [info] [ChronoLogClientImpl] Successfully created chronicle 'py_chronicle'.
[2025-01-21 13:47:57.120] [chrono_client] [warning] [StorytellerClient::findStoryWritingHandle] StoryHandle not found for Chronicle: 'py_chronicle' and Story: 'my_story'.
[2025-01-21 13:47:57.120] [chrono_client] [info] [RPCVisorClient] Initiating story acquisition: ChronicleName=py_chronicle, StoryName=my_story
[2025-01-21 13:47:57.121] [chrono_client] [info] [RPCVisorClient] Successfully acquired story: ChronicleName=py_chronicle, StoryName=my_story
[2025-01-21 13:47:57.129] [chrono_client] [error] [KeeperRecordingClient] Failed to create KeeperRecordingClient due to an exception.
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient] RUNNING with 1 KeeperRecordingClients
[2025-01-21 13:47:57.129] [chrono_client] [error] [KeeperRecordingClient] Failed to create KeeperRecordingClient due to an exception.
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient] RUNNING with 2 KeeperRecordingClients
[2025-01-21 13:47:57.129] [chrono_client] [error] [KeeperRecordingClient] Failed to create KeeperRecordingClient due to an exception.
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient] RUNNING with 3 KeeperRecordingClients
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient] Successfully initialized StoryWritingHandle for Chronicle: 'py_chronicle' and Story: 'my_story'.
[2025-01-21 13:47:57.129] [chrono_client] [info] [ChronoLogClientImpl] Successfully acquired story 'my_story' in chronicle 'py_chronicle'.
[2025-01-21 13:47:57.129] [chrono_client] [warning] [StoryWritingHandle] No keeper selected for logging event: py_event
[2025-01-21 13:47:57.129] [chrono_client] [warning] [StoryWritingHandle] No keeper selected for logging event: py_event.2
[2025-01-21 13:47:57.129] [chrono_client] [warning] [StoryWritingHandle] No keeper selected for logging event: py_event.3
[2025-01-21 13:47:57.129] [chrono_client] [warning] [StoryWritingHandle] No keeper selected for logging event: py_event.4
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient::findStoryWritingHandle] Found StoryHandle for Chronicle: 'py_chronicle' and Story: 'my_story'.
[2025-01-21 13:47:57.129] [chrono_client] [info] [StorytellerClient] Successfully removed StoryHandle for Chronicle: 'py_chronicle' and Story: 'my_story'.
[2025-01-21 13:47:57.129] [chrono_client] [info] [ChronoLogClientImpl] Successfully released the story 'my_story' from chronicle 'py_chronicle'.
[2025-01-21 13:47:57.129] [chrono_client] [info] [RPCVisorClient] Initiating story release: ChronicleName=py_chronicle, StoryName=my_story
[2025-01-21 13:47:57.130] [chrono_client] [info] [RPCVisorClient] Successfully released story: ChronicleName=py_chronicle, StoryName=my_story
[2025-01-21 13:47:57.130] [chrono_client] [info] [ChronoLogClientImpl] Successfully released story 'my_story' from chronicle 'py_chronicle'.
[2025-01-21 13:47:57.130] [chrono_client] [info] [RPCVisorClient] Initiating disconnection for ClientID=7014196618829343092
[2025-01-21 13:47:57.130] [chrono_client] [info] [RPCVisorClient] Disconnection successful for ClientID=7014196618829343092
[2025-01-21 13:47:57.130] [chrono_client] [info] [ChronoLogClientImpl] Successfully disconnected from Visor.

At the same time, this is something that does not happen when running the client_lib_multi_storytellers test. This test is able to run with no problems.

[ibrodkin]

It looks like the na_provider_string is missing the protocol fabric portion that should come before the endpoint ip address

It appears the bug of not passing the fabric into the na_ofi_lookup string was introduced shortly after release 1.0.1
I suggest we address this issue together with #156