when activate job gets a successful RPC response for the first time, it should not repeat the query; instead, just parse the output again and check whether the level is zero.
This way, if the second rpc query fails, it will just restart the job instead of passing silently, resulting in a non-activated chain stuck at level 0, as happened on Mondaynet today.
I tried:
private chain on minikube: I see the until loop run a few times, and then the chain gets activated
delete the activation job and run helm upgrade: job runs again, but is satisfied that activation already happened and exits silently
when activate job gets a successful RPC response for the first time, it should not repeat the query; instead, just parse the output again and check whether the level is zero.
This way, if the second rpc query fails, it will just restart the job instead of passing silently, resulting in a non-activated chain stuck at level 0, as happened on Mondaynet today.
I tried:
untilloop run a few times, and then the chain gets activatedhelm upgrade: job runs again, but is satisfied that activation already happened and exits silently