-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error fetching metrics #1578
Comments
Using concurrency of 1 does not fix the issue. |
Can the metrics endpoint be made optional? Not working would still be enough for integration tests. Maybe an explicit flag in the config file? |
Hey @ntn-x2, Thx! |
Hi @ntn-x2, are you running this on GH actions? can you enable the |
|
Sorry for the long output! Yes, it's a GH action. It seems to get stuck at the same point. |
Hey @ntn-x2, sorry about the delay. In my experience GH Actions with k8s/podman doesn't works well, some Thx! |
Hey, will have our DevOps guy take a look at it. Alternatively, we would have to cross-compile binaries instead of Docker images for the native provider to be used. Bit more involved tho. |
@pepoviola what is strange is that without the |
Also when properly enabling logs (adding the |
Hi @ntn-x2, sorry about the delay. Is this still an issue? I will close here and please re-open of needed. Thanks!! |
Hey @pepoviola, to be honest the problem did not go away (I used up to zombienet v1.3.85), and it got so frustrating that we decided to move to Chopsticks. If we happen to use Zombienet again, I will open a new issue in case I stumble into any problems. Thanks a lot! |
Hi @ntn-x2, again sorry about the delay and lack of solution. Please ping me if you consider moving to zombienet again and I we can revisit this and fix it for you and other teams. Thanks for your feedback! |
Issue Description
Kubernetes-based setup with the following config:
Network spawn with the following command
yarn zombienet --spawn-concurrency 3 spawn tests/zombienet/network.toml
.Relevant parts of GitHub CI configuration file:
Idea is to have the step to spin up the network run in the background with
&
, and have one more step listening for the ports:until (nc -w 3 127.0.0.1 ${{ env.RELAY_ALICE_RPC }} && nc -w 3 127.0.0.1 ${{ env.PROVIDER_ALICE_RPC }} && nc -w 3 127.0.0.1 ${{ env.CONSUMER_ALICE_RPC }}) ; do sleep 1; done
.The metrics problem stops the whole network from going up.
Additional details:
"@zombienet/cli": "^1.3.85"
.nvmrc
->lts/Hydrogen
(Node 18)Steps to reproduce the issue
Metrics errors seems arbitrary when running locally, but it always reproduce when running on the CI environment. See above for more details.
Describe the results you received
See above.
Describe the results you expected
See above.
Zombienet version
1.3.85
Provider
Kubernetes
Provider version
See above.
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Screenshots
No response
The text was updated successfully, but these errors were encountered: