Pre-flight checks for zowe init and startup #4276
Conversation
|
build 7423 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow09
GitHub Actions
Failure
|
Test workflow 6413 is started. |
|
build 7440 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
|
||
| common.printDebug(`Java ${javaVersionShort} is supported.`); | ||
| if (tooHigh) { | ||
| common.printMessage(`WARNING: Java ${javaVersionShort} is higher than the latest known working version for Zowe, v${JAVA_TESTED_VERSION}.`); |
There was a problem hiding this comment.
should probably omit warning when startupcheck for dependency is set false
| Copyright Contributors to the Zowe Project. | ||
| */ | ||
|
|
||
| import * as common from '../../../../libs/common'; |
There was a problem hiding this comment.
unsure if port-available is worth keeping if port-bind does the same and more.
|
Test workflow 6423 is started. |
|
build 7772 SUCCEEDED. |
|
Test workflow 6692 is started. |
|
build 7779 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
Test workflow 6698 is started. |
|
build 7780 SUCCEEDED. |
|
Test workflow 6699 is started. |
|
build 7781 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow09
GitHub Actions
Failure
|
Test workflow 6700 is started. |
|
build 7782 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow09
GitHub Actions
Failure
|
Test workflow 6701 is started. |
|
build 7797 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow10
GitHub Actions
Failure
|
Test workflow 6707 is started. |
zowe-robot
had a problem deploying
to
marist-zzow10
GitHub Actions
Failure
|
Test workflow 6707 is started. |
|
build 7798 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow09
GitHub Actions
Failure
|
Test workflow 6708 is started. |
|
build 7810 FAILED. |
|
build 7815 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow09
GitHub Actions
Failure
|
Test workflow 6723 is started. |
Signed-off-by: 1000TurquoisePogs <[email protected]>
… bin/utils folder Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
…icate validation. Use validators on zwe internal start prepare operation. Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
…EnabledComponents for zwe internal start prepare. Seemed to be a prior bug? Signed-off-by: 1000TurquoisePogs <[email protected]>
…ty about when to pass/fail on unknown errors Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: 1000TurquoisePogs <[email protected]>
1000TurquoisePogs
force-pushed
the
feature/v3/preflight-checks
branch
from
4b0c645 to
c031913
Compare
1000TurquoisePogs
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
build 8416 SUCCEEDED. |
zowe-robot
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
Test workflow 7169 is started. |
I am prototyping a set of utilities that can be invoked by
zwe validateby a user or zwe itself in order to check if a Zowe install is likely to run successfully or not prior to starting up all the servers and getting complex errors that users may not understand the meaning of.At this point nothing is set in stone. It is rather a place to dump ideas to return to later.
If this PR becomes more official, this description will be updated to reflect what it can do.
So far, the following exists:
zwe internal start preparealready does, so the code could be moved here to be reusableIt could be helpful to invoke these at the last step of
zwe initas well as at each startup, to catch as much user error as possible.I am intending to write a bypass, set in the YAML, so that if any validation fails it can be ignored rather than to prevent some execution, in case our validation logic itself is an error.