op-node service fails to spin up

[fgimenez]

Using the default op-node image we are getting these errors:

An error occurred executing instruction (number 53) at github.com/ethpandaops/optimism-package/src/cl/op-node/op_node_launcher.star[115:38]:
  add_service(name="op-cl-1-op-node-op-geth-op-kurtosis", config=ServiceConfig(image="us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:develop", ports={"http": PortSpec(number=8547, transport_protocol="TCP", application_protocol="http"), "metrics": PortSpec(number=9001, transport_protocol="TCP", application_protocol=""), "tcp-discovery": PortSpec(number=9003, transport_protocol="TCP", application_protocol="", wait=None), "udp-discovery": PortSpec(number=9003, transport_protocol="UDP", application_protocol="", wait=None)}, files={"/jwt": "op_jwt_file", "/network-configs": "op-deployer-configs"}, cmd=["op-node", "--l2=http://{{kurtosis:976b080617f14862a2235754f5af31e1:ip_address.runtime_value}}:8551", "--l2.jwt-secret=/jwt/jwtsecret", "--verifier.l1-confs=1", "--rollup.config=/network-configs/rollup-2151908.json", "--rpc.addr=0.0.0.0", "--rpc.port=8547", "--rpc.enable-admin", "--l1=http://{{kurtosis:8019dfdb86c84ba3ad30700f7a37338f:ip_address.runtime_value}}:8545", "--l1.rpckind=standard", "--l1.beacon=http://{{kurtosis:b5bcdee0be404baca48a24d18ff6e053:ip_address.runtime_value}}:4000", "--p2p.advertise.ip=KURTOSIS_IP_ADDR_PLACEHOLDER", "--p2p.advertise.tcp=9003", "--p2p.advertise.udp=9003", "--p2p.listen.ip=0.0.0.0", "--p2p.listen.tcp=9003", "--p2p.listen.udp=9003", "--safedb.path=/data/op-node/op-node-beacon-data", "--metrics.enabled=true", "--metrics.addr=0.0.0.0", "--metrics.port=9001", "--p2p.sequencer.key={{kurtosis:49f3aa6a69624857bc34407c9433b300:output.runtime_value}}", "--sequencer.enabled", "--sequencer.l1-confs=2"], env_vars={}, private_ip_address_placeholder="KURTOSIS_IP_ADDR_PLACEHOLDER", ready_conditions=ReadyCondition(recipe=PostHttpRequestRecipe(port_id="http", endpoint="/", body="{\"jsonrpc\":\"2.0\",\"method\":\"opp2p_self\",\"params\":[],\"id\":1}", content_type="application/json", extract={"enr": ".result.ENR", "multiaddr": ".result.addresses[0]", "peer_id": ".result.peerID"}), field="code", assertion="==", target_value=200, timeout="1m"), labels={"ethereum-package.client": "op-node", "ethereum-package.client-image": "us-docker.pkg.dev-oplabs-tools-artifacts-images-op-node_develop", "ethereum-package.client-type": "beacon", "ethereum-package.connected-client": "op-geth", "ethereum-package.sha256": ""}, tolerations=[], node_selectors={}))
  Caused by: Unexpected error occurred starting service 'op-cl-1-op-node-op-geth-op-kurtosis'
  Caused by: An error occurred waiting for all TCP and UDP ports to be open for service 'op-cl-1-op-node-op-geth-op-kurtosis' with private IP '172.16.0.22'; this is usually due to a misconfiguration in the service itself, so here are the logs:
  == SERVICE 'op-cl-1-op-node-op-geth-op-kurtosis' LOGS ===================================
  t=2025-02-08T12:21:45+0000 lvl=info msg="Not opted in to ProtocolVersions signal loading, disabling ProtocolVersions contract now."
  t=2025-02-08T12:21:45+0000 lvl=info msg="No persisted sequencer state loaded"
  t=2025-02-08T12:21:45+0000 lvl=info msg="Rollup Config" l2_chain_id=2151908 l2_network="unknown L2" l1_chain_id=3151908 l1_network="unknown L1" l2_start_time=1739017298 l2_block_hash=0xc10af175f048d8d9c74ea0c5abad8b0bfd6787a8c613e19fd57ef1230b8d9b33 l2_block_number=0 l1_block_hash=0x196f3ace988b31068eb3807db10cfef4bcacfacbc1fe8f571c887f4750ccdc43 l1_block_number=9 regolith_time="@ genesis" canyon_time="@ genesis" delta_time="@ genesis" ecotone_time="@ genesis" fjord_time="@ genesis" granite_time="@ genesis" holocene_time="@ genesis" isthmus_time="(not configured)" interop_time="(not configured)" alt_da=false
  t=2025-02-08T12:21:45+0000 lvl=info msg="Initializing rollup node" version=untagged-d554eeb3-1738969952
  t=2025-02-08T12:21:45+0000 lvl=info msg="Connected to L1 Beacon API, ready for EIP-4844 blobs retrieval." version=Lighthouse/v6.0.1-029b4f2/x86_64-linux
  t=2025-02-08T12:21:45+0000 lvl=info msg="Safe head database enabled" path=/data/op-node/op-node-beacon-data
  t=2025-02-08T12:21:45+0000 lvl=error msg="Error initializing the rollup node" err="failed to init L2: failed to load or fetch chain config for id 2151908: fetching: the method debug_chainConfig does not exist/is not available"
  t=2025-02-08T12:21:45+0000 lvl=crit msg="Application failed" message="failed to setup: unable to create the rollup node: failed to init L2: failed to load or fetch chain config for id 2151908: fetching: the method debug_chainConfig does not exist/is not available"
  
  == FINISHED SERVICE 'op-cl-1-op-node-op-geth-op-kurtosis' LOGS ===================================

See https://github.com/paradigmxyz/reth/actions/runs/13215444996/job/36894362688, this is our network config https://github.com/paradigmxyz/reth/blob/main/.github/assets/kurtosis_op_network_params.yaml

Setting and old op-node image like cl_image: "us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:a79e8cc06aa354511983fafcb6d71ab04cdfadbc" fixes the problem, looks like the issue was introduced here ethereum-optimism/optimism@4dcaec4

[fgimenez]

fixed after #160