docs: note that an absent systemrealm.cfg intentionally hangs startup#47
Merged
Merged
Conversation
After the system-realm activation-order fix, SystemBasedRealm is a mandatory Declarative Services dependency. When pnnl.goss.core.security.systemrealm.cfg is absent the realm never publishes, the mandatory reference never binds, and startup hangs with no broker. Document this fail-closed behavior in the production deployment troubleshooting guide so operators read the hang as a missing-config signal, not a platform bug.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a production-deployment troubleshooting note: after the system-realm activation-order fix (#1882),
SystemBasedRealmis a mandatory Declarative Services dependency declared withConfigurationPolicy.REQUIRE. Whenpnnl.goss.core.security.systemrealm.cfgis absent, the realm never publishes, the mandatory reference never binds, and startup hangs with no broker.Why
This is intentional fail-closed behavior (no insecure broker starts), but it presents as a silent hang with no obvious error. The note lets operators read the hang as a missing-config signal rather than a platform bug, with the remedy (ensure the cfg is present and mounted).
Related
Follows the #1882 fix. Tracking #40.