You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When setting up HA instances, one of the two would fail with this error, it apparently happens under some kind of race condition, as it worked after a couple of retries:
2023-03-27 13:25:55 <ZWELS:83952163> ZWESVUSR INFO (zwe-internal-start-prepare:360) starting Zowe instance lpar with /z/zwesvusr/api-layer-perf/zowe-vnightly-v2/zowe.yaml ...
2023-03-27 13:25:56 <ZWELS:83952163> ZWESVUSR DEBUG (zwe-internal-start-prepare,prepare_workspace_directory:36) initialize .instance-lpar.env(s)
Error: ENOENT: no such file or directory, open '/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/instance/workspace/.env/.zowe.json'
at Object.openSync (fs.js:507:3)
at Object.readFileSync (fs.js:400:35)
at simpleReadJson (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/src/libs/index.js:21:24)
at convertZoweYamlToEnv (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/src/libs/yaml.js:321:29)
at convertHaInstanceYamlToEnv (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/src/libs/yaml.js:412:3)
at Object.handler (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/src/commands/yaml.commands/to-env.js:48:5)
at /z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/node_modules/yargs/build/index.cjs:1:9052
at j (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/node_modules/yargs/build/index.cjs:1:4931)
at M.applyMiddlewareAndGetResult (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/node_modules/yargs/build/index.cjs:1:9021)
at M.runCommand (/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/utils/config-converter/node_modules/yargs/build/index.cjs:1:7206)
Try --help to get usage information, or use --verbose option to display more details.
!ïá<ë &ñ(<&äáêê|êÂÑ>%ÑÂËÄ?>ÃÑÅËÇÅÁ>ÁÊ/ÈÁ^Ñ>ËÈ/>ÄÁ^Á>Î^ÃÊ?_^`/_%^Ä?>ÃÑÅ!ïá<áã/Ñ%ÁÀÈ?ÈÊ/>Ë%/ÈÁ!?ÏÁÄ?>ÃÑÅÍÊ/ÈÑ?>:/øÑ_%øÄ/øÑ%/`ÁÊøÁÊÃ:?ÏÁÎ>ÑÅÇÈ%`Î:?ÏÁ`/_%2023-03-27 13:26:00 <ZWELNCH:83953947> ZWESVUSR WARN ZWEL0066W command 'APIML_SECURITY_SAF_URLS_AUTHENTICATE="https://zowe.lvn.domain.net:7555/zss/api/v1/saf/authenticate" EUREKA_SERVER_ENABLESELFPRESERVATION="false" _CEE_ENVFILE="DD:STDENV" _CEE_RUNOPTS="HEAPPOOLS(OFF)" CONFIG="/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/zowe.yaml" ROOT_DIR="/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime" /z/zwesvusr/api-layer-perf/zowe-vnightly-v2/runtime/bin/zwe internal start prepare --config "/z/zwesvusr/api-layer-perf/zowe-vnightly-v2/zowe.yaml" --ha-instance lpar 2>&1' ended with code 35840
2023-03-27 13:26:00 <ZWELNCH:83953947> ZWESVUSR ERROR ZWEL0030E failed to prepare Zowe instance
To Reproduce
Instances with default configuration, in HA mode. The STCs are launched one after the other one.
Expected behavior
Normal startup of Zowe.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When setting up HA instances, one of the two would fail with this error, it apparently happens under some kind of race condition, as it worked after a couple of retries:
To Reproduce
Instances with default configuration, in HA mode. The STCs are launched one after the other one.
Expected behavior
Normal startup of Zowe.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: