A new version of the ethereum-genesis-generator was pushed a few hours ago (here) and now the module is broken. It fails with this error:
Caused by: An error occurred launching a participant network of '4' participants
--- at /build/kurtosis-module/impl/module.go:90 (Eth2KurtosisModule.Execute) ---
Caused by: An error occurred generating EL client genesis data
--- at /build/kurtosis-module/impl/participant_network/participant_network.go:112 (LaunchParticipantNetwork) ---
Caused by: An error occurred executing command '[bash -c python3 /apps/el-gen/genesis_geth.py /config/genesis-config.yaml > /output/geth.json]' to create genesis config file '/output/geth.json'
--- at /build/kurtosis-module/impl/participant_network/prelaunch_data_generator/el_genesis/el_genesis_data_generator.go:155 (GenerateELGenesisData) ---
Caused by: Command '[bash -c python3 /apps/el-gen/genesis_geth.py /config/genesis-config.yaml > /output/geth.json]' should have returned 0 but returned 1 with the following output:
Traceback (most recent call last):
File "/apps/el-gen/genesis_geth.py", line 86, in <module>
"timestamp": str(data['genesis_timestamp'])
KeyError: 'genesis_timestamp'
--- at /build/kurtosis-module/impl/participant_network/prelaunch_data_generator/el_genesis/el_genesis_data_generator.go:207 (execCommand) ---
This genesis_timestamp is probably something new that was added to the generator, we should update the module accordingly.
cc @parithosh in case you followed what was changed in there.
Metapoint on this, the reason why it gets broken randomly is because we pin latest for all the images we use. We should pin a certain version to make sure things don't randomly start breaking. That being said, it seems in thie case the generator only published a latest version on docker hub, so we can't really pin a version here :(
A new version of the ethereum-genesis-generator was pushed a few hours ago (here) and now the module is broken. It fails with this error:
This
genesis_timestamp
is probably something new that was added to the generator, we should update the module accordingly. cc @parithosh in case you followed what was changed in there.Metapoint on this, the reason why it gets broken randomly is because we pin
latest
for all the images we use. We should pin a certain version to make sure things don't randomly start breaking. That being said, it seems in thie case the generator only published alatest
version on docker hub, so we can't really pin a version here :(