Open ZuitAMB opened 2 months ago
Thanks for the detailed description, we'll look at it!
Might have been fixed by https://github.com/openkfw/TruBudget/pull/1983 ?
Yes, the provisioning improves might have fixed the issue. I will check it on our next Beta node connection.
@ZuitAMB can you confirm this was fixed by #1983 ? Or is there a need to further updates?
Description 😯
When running a multi node setup and connecting a new beta node to a pre existing alpha node, the connection and synchronization process takes some time. First, the alpha node needs to accept the join request. Second, the nodes have to synchronize the data, which also might take some time.
The provisioning service offers the possibility to provision data, like users.
In combination, the provisioning service might terminate, before the nodes are synchronized, which leads to the users not being provisioned. (Or if the blockchain is ready, after half of the users were tried to provision, only parts of the data would be provisioned.
How to reproduce 🕹
Current workaround
It is possible to manually stop the provisioning container and start it, once the nodes are connected and synchronized. However, such a manual interaction is subpar.
Possible Fix/Solution
The beta node provisioning should wait until the blockchain node is ready (connected and synchronized)
Your Environment 🌎