ethereum_package geth fails to spin up

[samlaf]

When running kurtosis run github.com/ethpandaops/optimism-package --args-file https://raw.githubusercontent.com/ethpandaops/optimism-package/main/network_params.yaml, get

Adding service with name 'el-1-geth-lighthouse' and image 'ethereum/client-go:latest'
There was an error executing Starlark code 
An error occurred executing instruction (number 24) at github.com/ethpandaops/ethereum-package/src/el/geth/geth_launcher.star[74:31]:
  add_service(name="el-1-geth-lighthouse", config=ServiceConfig(image="ethereum/client-go:latest", ports={"engine-rpc": PortSpec(number=8551, transport_protocol="TCP", application_protocol=""), "metrics": PortSpec(number=9001, transport_protocol="TCP", application_protocol="http"), "rpc": PortSpec(number=8545, transport_protocol="TCP", application_protocol=""), "tcp-discovery": PortSpec(number=30303, transport_protocol="TCP", application_protocol=""), "udp-discovery": PortSpec(number=30303, transport_protocol="UDP", application_protocol=""), "ws": PortSpec(number=8546, transport_protocol="TCP", application_protocol="")}, public_ports={}, files={"/jwt": "jwt_file", "/network-configs": "el_cl_genesis_data"}, entrypoint=["sh", "-c"], cmd=["geth init --datadir=/data/geth/execution-data /network-configs/genesis.json && geth    --networkid=3151908 --verbosity=3 --datadir=/data/geth/execution-data --http --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=admin,engine,net,eth,web3,debug --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=admin,engine,net,eth,web3,debug --ws.origins=* --allow-insecure-unlock --nat=extip:KURTOSIS_IP_ADDR_PLACEHOLDER --authrpc.port=8551 --authrpc.addr=0.0.0.0 --authrpc.vhosts=* --authrpc.jwtsecret=/jwt/jwtsecret --syncmode=full --rpc.allow-unprotected-txs --metrics --metrics.addr=0.0.0.0 --metrics.port=9001 --discovery.port=30303 --port=30303"], env_vars={}, private_ip_address_placeholder="KURTOSIS_IP_ADDR_PLACEHOLDER", labels={"ethereum-package.client": "geth", "ethereum-package.client-image": "ethereum-client-go_latest", "ethereum-package.client-type": "execution", "ethereum-package.connected-client": "lighthouse", "ethereum-package.sha256": ""}, tolerations=[], node_selectors={}))
  Caused by: Unexpected error occurred starting service 'el-1-geth-lighthouse'
  Caused by: An error occurred waiting for all TCP and UDP ports to be open for service 'el-1-geth-lighthouse' with private IP '172.16.0.9'; this is usually due to a misconfiguration in the service itself, so here are the logs:
  == SERVICE 'el-1-geth-lighthouse' LOGS ===================================
  INFO [02-10|06:21:07.128] Maximum peer count                       ETH=50 total=50
  INFO [02-10|06:21:07.129] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
  INFO [02-10|06:21:07.132] Set global gas cap                       cap=50,000,000
  INFO [02-10|06:21:07.132] Initializing the KZG library             backend=gokzg
  INFO [02-10|06:21:07.151] Defaulting to pebble as the backing database
  INFO [02-10|06:21:07.151] Allocated cache and file handles         database=/data/geth/execution-data/geth/chaindata cache=16.00MiB handles=16
  INFO [02-10|06:21:07.168] Opened ancient database                  database=/data/geth/execution-data/geth/chaindata/ancient/chain readonly=false
  INFO [02-10|06:21:07.168] State schema set to default              scheme=path
  ERROR[02-10|06:21:07.169] Head block is not reachable
  INFO [02-10|06:21:07.187] Opened ancient database                  database=/data/geth/execution-data/geth/chaindata/ancient/state readonly=false
  INFO [02-10|06:21:07.187] Initialized path database                cache=16.00MiB buffer=64.00MiB history=90000
  INFO [02-10|06:21:07.187] Writing custom genesis block
  Fatal: Failed to write genesis block: unsupported fork configuration: missing blob configuration entry for cancun in schedule
  Fatal: Failed to write genesis block: unsupported fork configuration: missing blob configuration entry for cancun in schedule
  
  == FINISHED SERVICE 'el-1-geth-lighthouse' LOGS ===================================
  Caused by: An error occurred while waiting for all TCP and UDP ports to be open
  Caused by: Unsuccessful ports check for IP '172.16.0.9' and port spec '{privatePortSpec:0x4000948f90}', even after '240' retries with '500' milliseconds in between retries. Timeout '2m0s' has been reached
  Caused by: An error occurred while calling network address '172.16.0.9:8551' with port protocol 'TCP' and using time out '200ms'
  Caused by: dial tcp 172.16.0.9:8551: connect: no route to host

Error encountered running Starlark code.

Fairly certain this is going to get fixed once ethpandaops/ethereum-package#891 is merged.
However ethereum-package will prob have to create a new package at that point and we'll have to update

optimism-package/kurtosis.yml

Line 6 in c32a626

github.com/ethpandaops/ethereum-package: github.com/ethpandaops/ethereum-package@4.4.0

to point to this new version.

[0xOsiris]

Hey guy's do we have an ETA on this - this breaks all testing environments using the optimism-package?

[samlaf]

@0xOsiris ethereum-package 4.5.0 was released, just update your kurtosis.yaml file to point to that. @parithosh is making a PR to update it here as well, but you can make the change locally in the meantime.

However there's another issue right now which I'm facing: ethpandaops/ethereum-package#899

[samlaf]

EDIT: managed to spin up op-package by changing ethereum-package's preset to mainnet, but seeing this weird error log, not sure if its impacting anything:

Collect keys, and fund addresses
Command returned with exit code '0' and the following output:
--------------------
Wallet private key and addresses
{
  "2151908": {
    "proposerPrivateKey": "0x9d77c0558ed6f31e7be16c2f45fd1f3ec3f66d20526b7fe3961872d38ac98fe7",
    "proposerAddress": "0xb0994E702b603df7191cd68E6544f99126135e34",
    "batcherPrivateKey": "0xb3d2d558e3491a3709b7c451100a0366b5872520c7aa020c17a0e7fa35b6a8df",
    "batcherAddress": "0xD3F2c5AFb2D76f5579F326b0cD7DA5F5a4126c35",
    "sequencerPrivateKey": "0x459f58fd8ef3d9123333514d0f2445153fc29ddc43be239356dad70f506475d9",
    "sequencerAddress": "0xbb900Cf56918A2639dAA90c3f7DC5DCD2f5B9935",
    "challengerPrivateKey": "0x717c53f6d6c266889465d78a885cd0a2e22d41f73e21fa1f07ba5849c82d79c3",
    "challengerAddress": "0xf08f610d1956CAAAb34f18e9e0A122E389496529",
    "l2ProxyAdminPrivateKey": "0x93be1ab4efe7633d951f19783912817a264f70889cc230e6015627695041744b",
    "l2ProxyAdminAddress": "0x21DD8D15472844b905E603Ddd48A485a630B233b",
    "l1ProxyAdminPrivateKey": "0xa8574059a5e36acd4d6ea03e90fe8b5233cc87222b0b396f9b1d6f3e5d6368fa",
    "l1ProxyAdminAddress": "0x39Dc844B8b461c6de6c572cad9585d9f5A8DEa6A",
    "baseFeeVaultRecipientPrivateKey": "0x227e712ee48868fff4651301e8f366bea05e822db3429470bbc7ed2ee045cb67",
    "baseFeeVaultRecipientAddress": "0x9ef74F0e58fdEf70c11E587A45c0a85A3258DCeA",
    "l1FeeVaultRecipientPrivateKey": "0xe6414f68c9f0d5e3470955a39c1af602a3132f709130fea6304f126a78b7f6aa",
    "l1FeeVaultRecipientAddress": "0xA7B30F9e99A248C6D623eaaD7bce81217Bb84038",
    "sequencerFeeVaultRecipientPrivateKey": "0xc11b0cec865b74505976f6c7fc5736a701f1cdf9e46aa72c02d51c0fe6ec3fed",
    "sequencerFeeVaultRecipientAddress": "0x15947bF05662caD8DF55f004c055939b574f18c0",
    "systemConfigOwnerPrivateKey": "0x28978385446dde6ce493da611d6c9ae6193d960c1cb73ecfb25800e9c9017f4c",
    "systemConfigOwnerAddress": "0x8e44fEbeaE9C2F2Bc89480aE8084328Badc496c2",
    "l1FaucetPrivateKey": "0x04b9f63ecf84210c5366c66d68fa1f5da1fa4f634fad6dfc86178e4d79ff9e59",
    "l1FaucetAddress": "0xafF0CA253b97e54440965855cec0A8a2E2399896",
    "l2FaucetPrivateKey": "0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80",
    "l2FaucetAddress": "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266"
  }
}
ErrorError:: transaction was not confirmed within the timeout
 transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout
Error: transaction was not confirmed within the timeout

[samlaf]

Fixed by #160