Thanks to visit codestin.com
Credit goes to github.com

Skip to content

bug: in air-gapped kubernetes cluster, coderd deployment crashloops #6258

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

Closed
johnstcn opened this issue Feb 17, 2023 · 4 comments · Fixed by #6263
Closed

bug: in air-gapped kubernetes cluster, coderd deployment crashloops #6258

johnstcn opened this issue Feb 17, 2023 · 4 comments · Fixed by #6263
Assignees
Labels
site Area: frontend dashboard

Comments

@johnstcn
Copy link
Member

johnstcn commented Feb 17, 2023

Observed during customer call: get UI error "something went wrong" intermittently.
Appears to only happen on air-gapped cluster that cannot access internet.

Steps to reproduce (reproduced on OpenShift 4.12 single-node):

  • Install Coder in Kubernetes via Helm Chart
  • Create NetworkPolicies that only allow traffic within the cluster
  • Observe coder pod crashing periodically with following message:
    Unexpected error, shutting down server: install terraform: install: Get "https://releases.hashicorp.com/terraform/1.3.4/index.json": dial tcp 143.204.68.20:443: i/o timeout
    
@johnstcn johnstcn added the bug label Feb 17, 2023
@kylecarbs kylecarbs added the site Area: frontend dashboard label Feb 17, 2023
@johnstcn johnstcn self-assigned this Feb 17, 2023
@johnstcn johnstcn changed the title bug: ui: "something went wrong" when checking for updates from air-gapped cluster bug: in air-gapped cluster, coderd deployment crashloops Feb 17, 2023
@johnstcn johnstcn changed the title bug: in air-gapped cluster, coderd deployment crashloops bug: in air-gapped kubernetes cluster, coderd deployment crashloops Feb 17, 2023
@bpmct
Copy link
Member

bpmct commented Feb 18, 2023

there's also flickering on the deployment due to the check for updates... should we use a different ticket to track that?

@BrunoQuaresma
Copy link
Collaborator

@johnstcn is it at a specific route?

@johnstcn
Copy link
Member Author

@BrunoQuaresma it's /api/v2/workspaces/$WORKSPACE_ID/watch

@johnstcn
Copy link
Member Author

johnstcn commented Mar 13, 2023

#6541 fixed the UI piece of this.

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

Successfully merging a pull request may close this issue.

4 participants