-
Bug
-
Resolution: Done
-
Normal
-
4.8.0
-
Moderate
-
None
-
Rejected
-
False
-
Description of problem:
Users on a fully-disconnected cluster could not see Devfiles in the developer catalog or import a Devfiles. That's fine.
But the API calls /api/devfile/samples/ and /api/devfile/ takes 30 seconds until they fail with a 504 Gateway timeout error.
If possible they should fail immediately.
Version-Release number of selected component (if applicable):
This might happen since 4.8
Tested this yet only on 4.12.0-0.nightly-2022-09-07-112008
How reproducible:
Always
Steps to Reproduce:
- Start a disconnected cluster with a proxy
- Open the browser network inspector and filter for /api/devfile
- Switch to Developer perspective
- Navigate to Add > Developer Catalog (All Services) > Devfiles
- Or Add > Import from Git > and enter https://github.com/devfile-samples/devfile-sample-go-basic.git
Actual results:
- Network call fails after 30 seconds
- Import doesn't work
Expected results:
- Network calls should fail immediately
- We doesn't expect that the import will work
Additional info:
The console Pod log contains this error:
E0909 10:28:18.448680 1 devfile-handler.go:74] Failed to parse devfile: failed to populateAndParseDevfile: Get "https://registry.devfile.io/devfiles/go": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
- clones
-
OCPBUGS-2716 Devfile Catalog and Import a Devfile on a fully disconnected cluster should fail directly instead of timeout after 30sec
- Closed
- depends on
-
OCPBUGS-2716 Devfile Catalog and Import a Devfile on a fully disconnected cluster should fail directly instead of timeout after 30sec
- Closed
- is cloned by
-
OCPBUGS-2718 Devfile Catalog and Import a Devfile on a fully disconnected cluster should fail directly instead of timeout after 30sec
- Closed
- is depended on by
-
OCPBUGS-2718 Devfile Catalog and Import a Devfile on a fully disconnected cluster should fail directly instead of timeout after 30sec
- Closed
- links to