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
If logs are written to directories within the Zowe installation home, as seen in one case under the components subdirectory, then verify fingerprints may either fail or pass depending on where the log is placed. In practice, the behavior should be consistent and opinionated - either log files under the install directory are tolerated and verify fingerprint should always pass, or they are not tolerated and fingerprint verification should always fail.
To Reproduce
Steps to reproduce the behavior:
Run a build where the log directory is unset. This triggers app framework components to log under the components directory.
Run verify fingerprints.
Verify fingerprint fails
Note: we had a case where ZSS logged under components and app framework did not, and fingerprints passed. When both components logged under components, fingerprints failed. Exact reason unknown.
Expected behavior
See description
Additional context
This can be worked around by deleting or moving any application logs under the runtime directory. Pattern ~ */log/*.log.
Setting the log directory in zowe.yaml to a location outside the install directory should avoid this bug altogether, however, there is a separate bug <2.10.0 where log directory may not be sent to app framework components resulting in them logging to a subdirectory under the components dir.
The text was updated successfully, but these errors were encountered:
- Find different files
* Number of different files: 1
* All different files:
./components/app-server/share/zlux-app-server/log/appServer-2024-08-08-14-37.log -2064295117616972499
./components/zss/log/zssServer-2024-08-08-14-37.log 3299772109190652281
- Find extra files
* Number of extra files: 1
* All extra files:
./components/app-server/share/zlux-app-server/log/appServer-2024-08-08-14-37.log -2064295117616972499
./components/zss/log/zssServer-2024-08-08-14-37.log 3299772109190652281
- Find missing files
* Number of missing files: 0
- Clean up temporary files...
zwe support requires zowe.yaml, it is able (with some code changes) to exclude the log directory or use the suggested pattern if no log directory is set.
But you can also call zwe support verify-fingerprints directly and this command does not require zowe.yaml and has no idea, where the logs are.
Describe the bug
If logs are written to directories within the Zowe installation home, as seen in one case under the
components
subdirectory, then verify fingerprints may either fail or pass depending on where the log is placed. In practice, the behavior should be consistent and opinionated - either log files under the install directory are tolerated and verify fingerprint should always pass, or they are not tolerated and fingerprint verification should always fail.To Reproduce
Steps to reproduce the behavior:
components
directory.Note: we had a case where ZSS logged under
components
and app framework did not, and fingerprints passed. When both components logged under components, fingerprints failed. Exact reason unknown.Expected behavior
See description
Additional context
This can be worked around by deleting or moving any application logs under the runtime directory. Pattern ~
*/log/*.log
.Setting the log directory in zowe.yaml to a location outside the install directory should avoid this bug altogether, however, there is a separate bug <2.10.0 where log directory may not be sent to app framework components resulting in them logging to a subdirectory under the
components
dir.The text was updated successfully, but these errors were encountered: