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

[Devsandbox] Failures during the project import after Get Started workspace startup - Couldn't import http://172.30.145.30:8080/resources/quarkus-quarkus-quickstarts-main.zip: curl: (7) Failed to connect to 172.30.145.30 port 8080: Connection timed out #19853

Closed
ibuziuk opened this issue May 24, 2021 · 3 comments
Assignees
Labels
area/hosted-che kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Comments

@ibuziuk
Copy link
Member

ibuziuk commented May 24, 2021

Describe the bug

Che version

CRW 2.8

Steps to reproduce

  1. Go to Get Started Tab workspaces.openshift.com#get-started
  2. Start one of the samples e.g. quarkus
  3. ERROR: workspace is started but the project can not be imported:

image

Expected behavior

Workspace started without problems

Runtime

  • OSD 4.7

Eclipse Che Logs

Additional context

devfile of the created workspace looks bizarre and reference to the cluster-specific zip source:

projects:
  - name: quarkus-quickstarts
    source:
      location: 'http://172.30.59.26:8080/resources/quarkus-quarkus-quickstarts-main.zip'
      type: zip
@ibuziuk ibuziuk added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels May 24, 2021
@ibuziuk ibuziuk self-assigned this May 24, 2021
@ibuziuk
Copy link
Member Author

ibuziuk commented May 24, 2021

Dogfooding instance and https://www.eclipse.org/che/getting-started/cloud/ are also affected

@ibuziuk
Copy link
Member Author

ibuziuk commented May 24, 2021

The culprit is the incorrect cluster-specific location to the zip files e.g.:

- name: quarkus-quickstarts
    source:
      location: 'http://172.30.189.177:8080/resources/quarkus-quarkus-quickstarts-main.zip'
      type: zip

@ibuziuk ibuziuk changed the title [Devsandbox] Failures during the project import after Get Satrted workspace startup - Couldn't import http://172.30.145.30:8080/resources/quarkus-quarkus-quickstarts-main.zip: curl: (7) Failed to connect to 172.30.145.30 port 8080: Connection timed out [Devsandbox] Failures during the project import after Get Started workspace startup - Couldn't import http://172.30.145.30:8080/resources/quarkus-quarkus-quickstarts-main.zip: curl: (7) Failed to connect to 172.30.145.30 port 8080: Connection timed out May 24, 2021
@ibuziuk
Copy link
Member Author

ibuziuk commented May 24, 2021

The issue has been fixed on workspaces.openshift.com.
Until there will be a proper implementation [1] of support of both internal & external registries the SOP for fixing the setup is:

  • switching CR back to the internal registry:
    - remove devfileRegistryUrl from CR
    - set externalDevfileRegistry: false
  • restarting the devfile registry pod (CHE_DEVFILE_REGISTRY_URL should be set [2] correctly now)
    - just delete the devfile registry pod (it will be re-created with the right env var)
  • setting back the external registries in CR (internal + community):
    - set externalDevfileRegistry: true
    - set `devfileRegistryUrl: link_to_internal_registry link_to_external_registry"

[1] #19781
[2] https://github.com/redhat-developer/codeready-workspaces/blob/crw-2-rhel-8/dependencies/che-devfile-registry/build/scripts/cache_projects.sh#L54

@ibuziuk ibuziuk closed this as completed May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/hosted-che kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

1 participant