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.

Sign up for GitHub

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

Jump to bottom

zarf tools registry pull - i/o time out error #1929

Closed
Arsinic opened this issue Jul 28, 2023 · 1 comment · Fixed by #1930
Closed

zarf tools registry pull - i/o time out error #1929

Arsinic opened this issue Jul 28, 2023 · 1 comment · Fixed by #1930
Labels
possible-bug 🐛

Comments

@Arsinic
Copy link

Arsinic commented Jul 28, 2023

Environment

Device and OS: Mac book Pro local & eks gitlab runner
App version: v0.28.3
Kubernetes distro being used: eks on the runner
Other:

Steps to reproduce

  1. Using zarf version 0.28.3 attempt to zarf tools registry pull ghcr.io/defenseunicorns/zarf/agent:v0.28.3 ./zarf (the pulled image doesn't matter). The command always gives a timeout.

Expected result

The zarf command pulls images

Actual Result

Error: Get "<some non existant / unreachable cluster that exists in .kube/config": dial tcp <that.clusters.ip.addr>:443: i/o timeout

Visual Proof (screenshots, videos, text, etc)

image

Severity/Priority

Additional Context

Rolling back zarf version to v0.28.0 seemed to correct the issue, although that could be unrelated.
@Racer159 Racer159 mentioned this issue Jul 29, 2023
Merged
5 tasks
@Racer159
Copy link
Contributor

This is because a ~/.kube/config was found by Zarf but contains a cluster that cannot be reached or one that does not have Zarf state - v0.28.0 did not have the code that tries to lookup Zarf state which resolves this issue as well. Pushed a PR though that will flag a warning instead of a hard error going forward.

Noxsios added a commit that referenced this issue Aug 1, 2023
@Racer159 @Noxsios
Fix a bug with registry push/pull on detected but invalid clusters (#…
5f4151f 
…1930)

## Description

This fixes an issue with zarf tools registry where an invalid cluster
(one that was not connectable or did not have state) could cause a
failure.

## Related Issue

Fixes #1929 

## 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

---------

Co-authored-by: razzle <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
possible-bug 🐛
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix a bug with registry push/pull on detected but invalid clusters zarf-dev/zarf
2 participants
@Racer159 @Arsinic