Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale.
Describe the bug
When using the SetupEntryPoint to call a batch script at startup the script will exit with status code 0 to indicate it successfully completed, however SFX is still showing these process exited events and Unexpected and marking them as errors. this makes it hard to track when the scripts are actually failing.
Describe the bug When using the SetupEntryPoint to call a batch script at startup the script will exit with status code 0 to indicate it successfully completed, however SFX is still showing these process exited events and Unexpected and marking them as errors. this makes it hard to track when the scripts are actually failing.
Area/Component: Monitoring?
To Reproduce Steps to reproduce the behavior:
Expected behavior I would expect the startup script to exit with status 0 to indicate a success and there should be no error events.
Observed behavior:
Screenshots
Service Fabric Runtime Version: 9.0.*
Environment: Standalone but also on azure clusters
If this is a regression, which version did it regress from? no
Assignees: /cc @microsoft/service-fabric-triage