-
Type:
Bug
-
Resolution: Tracked Elsewhere
-
Priority:
Medium
-
Component/s: Forge - Function invocation
-
Severity 2 - Major
-
Resiliency
Issue Summary
Few forge apps are unable to use the storage API. The issue seems to be inconsistent now.
Steps to Reproduce
- Create an app that interacts with the Forge Storage
- Attempt to fetch data from it using kvs.query()
Expected Results
Storage API should work consistently
Actual Results
The below exception is thrown in the app logs:
TypeError: fetch failed
at e.exports.fetch (/mnt/wrapper/wrapper_v20_15.cjs:2:1008204)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async d (/mnt/wrapper/wrapper_v20_15.cjs:2:1038686)
at async GlobalStorage.apiClient (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/api/out/api/fetch.js:20:1)
at async GlobalStorage.query (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/storage/out/global-storage.js:109:1)
at async <anonymous> (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/storage/out/global-storage.js:91:46)
at async GlobalStorage.wrapInMetric (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/storage/out/global-storage.js:130:1)
at async GlobalStorage.getInternal (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/storage/out/global-storage.js:91:46)
at async <anonymous> (webpack://jira-project-settings-page-custom-ui/src/index.js:432:22)
at async Object.resolve (webpack://jira-project-settings-page-custom-ui/node_modules/@forge/resolver/out/index.js:55:1) {
[cause]: ConnectTimeoutError: Connect Timeout Error (attempted addresses: 10.1.0.4:443, 10.1.0.39:443, 10.1.0.28:443, timeout: 10000ms)
at l (/mnt/wrapper/wrapper_v20_15.cjs:2:1079086)
at Immediate._onImmediate (/mnt/wrapper/wrapper_v20_15.cjs:2:1078714)
at process.processImmediate (node:internal/timers:483:21)
at process.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available.