-
Notifications
You must be signed in to change notification settings - Fork 12
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
Failing to run bundle_v2 integration tests running out of space #426
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5553.
|
I think this has occurred because of at least two things:
It appears that because of (2), the A possible solution to this issue is to switch to the the jlumbroso/free-disk-space action which, with default settings, leaves the runner with ~45GB free. |
Nice quick way for unblocking us @ca-scribner! For the long term solution I propose that we'll go with self-hosted runners #428 (comment) I had tried to play a bit around with those in #415 and #414. I'll do a cleanup and have also a dedicated PR and issue for this so we laser focus it on the changes we'll need to do holistically. I'll have them ready by the sprint so that we can sit down with IS team and show them our blockers. I'll add a comment here as well so that the lineage of the effort is tracked. |
Bug Description
When running CI the
test bundle v2
fails. After sshing into the runner we found out the main problem is insufficient amount of disk space causing pods stopping in pending state withdf command from inside the runner:
This issue is similar to this one canonical/bundle-kubeflow#813
To Reproduce
main
against main to trigger CIEnvironment
Github actions CI in main branch
Relevant Log Output
Additional Context
No response
The text was updated successfully, but these errors were encountered: