You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a network bandwidth experiment on an existing network, chaos-mesh fails to start. The returned error is "chaos-mesh is still in a 'starting' state after 10 seconds. "
Not that the same setup (running an existing kurtosis testnet) for memory-stress test works.
Logs
All the pods in namespaces (chaos-mesh, kt-relaytestnet, and kurtosis-engine) running as expected in Kubernetes
Launch attack scenario metaclear-network-bandwidth...
INFO[0000] Loading test suite from /Users/qyu/attacknet/test-suites/metaclear-network-bandwidth.yaml
INFO[0000] Loading kurtosis network configuration from /Users/qyu/attacknet/network-configs/metaclear-relayer-devnet.yaml
INFO[0001] Looking for existing enclave identified by namespace kt-relaytestnet
INFO[0030] An active enclave matching kt-relaytestnet was found
INFO[0030] Creating a chaos-mesh client
INFO[0030] Waiting 50 seconds before starting fault injection
INFO[0080] Running 1 tests
INFO[0080] Running test (1/1): 'metaclear-network-bandwidth'
INFO[0080] Running test step (1/2): 'inject fault to beacon client'
ERRO[0090] Error while running test #1
FATA[0090] chaos-mesh is still in a 'starting' state after 10 seconds. Check kubernetes events to see what's wrong.
--- at /Users/qyu/attacknet/pkg/test_executor/executor.go:152 (waitForInjectionCompleted) ---
Description
When running a network bandwidth experiment on an existing network, chaos-mesh fails to start. The returned error is "chaos-mesh is still in a 'starting' state after 10 seconds. "
Not that the same setup (running an existing kurtosis testnet) for memory-stress test works.
Logs
All the pods in namespaces (chaos-mesh, kt-relaytestnet, and kurtosis-engine) running as expected in Kubernetes
Log printed in console:
Config
YAML config file for attacknet
The text was updated successfully, but these errors were encountered: