Skip to content
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

Sideloading image gives ('Connection aborted.', OSError("(104, 'ECONNRESET')")) error #4304

Open
senyahnoj opened this issue Nov 15, 2023 · 9 comments

Comments

@senyahnoj
Copy link

Summary

When sideloading a container image in microk8s 1.27.7 it fails with the following error

Failed to reach 10.0.2.15:25000: ('Connection aborted.', OSError("(104, 'ECONNRESET')"))

I have installed microk8s 1.27.7 on RHEL 8.8 linux via the snap store

I have the same version of microk8s on an ubuntu linux server (20.04) and I do not experience the same issue

What Should Happen Instead?

The image should be sideloaded into containerd

Reproduction Steps

  1. Install microk8s via the snap store
  2. Ran
sudo microk8s images import /tmp/mycontainerimage.tar

Screenshot from 2023-11-15 14-55-06

Introspection Report

inspection-report-20231115_144720.tar.gz

@neoaggelos
Copy link
Contributor

Hi @senyahnoj, thank you for reporting the issue. This should be resolved in the latest version with canonical/microk8s-cluster-agent#52, but we have not backported the fix.

I think we should backport that fix to 1.28, 1.27 and previous branches as well.

In the meantime, if you have a test environment could you test microk8s from the latest/edge channel (sudo snap install microk8s --channel latest/edge --classic) and see whether the issue is resolved? Thanks!

@senyahnoj
Copy link
Author

senyahnoj commented Nov 15, 2023

Thanks for your reply @neoaggelos. I confirm that when using latest/edge --classic (1.28.3), the issue is resolved.

A backport to both 1.28 and 1.27 would be very much appreciated if possible

@senyahnoj
Copy link
Author

Is there any timescale for releasing 1.28.4 into the stable channel with this fix?

@neoaggelos
Copy link
Contributor

Hi @senyahnoj, sorry for taking long to reply. We have recently had some bumps in our release pipelines, but things should be resolved now. New patchlevel releases are pushed to stable a week after they're out, so next week should do it:

$ snap info microk8s | grep '1.28/'
  1.28/stable:           v1.28.3  2023-11-12 (6089) 185MB classic
  1.28/candidate:        v1.28.6  2024-01-28 (6429) 185MB classic
  1.28/beta:             v1.28.6  2024-01-28 (6429) 185MB classic
  1.28/edge:             v1.28.6  2024-01-17 (6429) 185MB classic

@senyahnoj
Copy link
Author

Thank you so much @neoaggelos for your reply

@senyahnoj
Copy link
Author

@neoaggelos still no release. Are we still expecting one?

@DileepAP
Copy link

@neoaggelos Any updates on the release date for this issue.

@neoaggelos
Copy link
Contributor

Hi @senyahnoj @DileepAP, apologies. We unfortunately had some bumps in our release pipeline, but things should now be resolved and fixes are out in all stable tracks.

@paddyabc
Copy link

paddyabc commented Nov 21, 2024

I just installed v1.31.2 (stable version) today and I face the same issue in v1.31.2 (stable version)
But I installed the microk8s in Ubuntu 24.04 LTS instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants