-
Notifications
You must be signed in to change notification settings - Fork 174
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
Pushing Images to zarf registry hangs forever #1218
Comments
The image push eventually finished but is happening on other images as well where they're taking way too long to push to registry for their size/this hardware |
Pod that was handling the image push was scaled out and deleted |
CLI error |
Same error when pod isn't scaled out |
All http PUTs seem to work fine, every time a hang starts it's on an http PATCH but not every PATCH fails |
PATCH log that never completes
|
New error
|
Restarting my machine seems to have solved this however I want to leave this issue open to discuss building a better mechanism around detected lost connections when pushing images |
Restarting only works for first cluster stood up after restart, if that cluster is torn down and another is started the issue resurfaces. My current workaround is to run |
When the tunnel is failing it would be great to see the k8s events and the pod logs at the same time. |
OS is Ubuntu Server 20.04 LTS root@rke1: Running into same error with zarf package deploy command. It hangs on deploying the fluxcd/helm-controller. Furthermore, it has hung on zarf init pulling the gitea package as well. |
Failing on zarf init @jeff-mccoy
registry log:
zarf.log |
events in zarf namespace during failure:
|
k3d.agent.log |
Zarf init managed to finish with some retries. Waiting on a different deployment with more/larger images to fail now. Cycle seems to be as follows
|
zarf-2023-01-24-16-13-38-334878943.log |
As a side note while zarf is failing to push an image, even if you delete the registry pod it doesn't realize that there is no longer a connection |
This is not a reliable fix. Still can happen when running this command. |
And it's also still happening directly after a restart |
Happened again but on different hardware/software: |
I have the same issue. Intermittent hanging on pushes to registry. |
I'm using |
## Description This enables some additional logging information for pushes to registries. ## Related Issue Relates to #1218 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [x] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
…ushes (#1590) ## Description This PR creates a tunnel per image push (making it easier to implement concurrency - may do that in this PR if we can confirm that issues are mitigated) moves the CRC from the image name to the tag and changes the UI to use a progressbar instead of a spinner for better user feedback. ## Related Issue Relates to #1568 , #1433, #1218, #1364 This also will make #1594 slightly easier. (See aws/containers-roadmap#853) Fixes: #1541 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
@corang have you gotten a chance to try v0.26.0 and have you seen any intermittent issues with that? |
I have not, but I also haven't had any issues with image pushes since I stopped using k3s/rke2 for things and now use kind for everything |
Going to close in favor of troubleshooting this further in #1568 |
Environment
Device and OS: Ubuntu 22
App version: 0.23.2+
Kubernetes distro being used: k3s in k3d
k8s version: v1.24.4+k3s1
Other:
Steps to reproduce
Expected result
All images are pushed to registry and package deployment continues
Actual Result
Sometimes the package is pushed successfully (looking at registry logs) but the zarf CLI just hangs forever on "Updating Image xxx"
Visual Proof (screenshots, videos, text, etc)
Has been on this image effectively the entire time
Severity/Priority
High, I can't use zarf as it is now
Additional Context
The text was updated successfully, but these errors were encountered: