fix(ops): refresh stale 2FA bot bind mounts - #107
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
🤖 Codex PR Review✅ Merge allowed: No issues found Review by Codex PR Review bot • PR |
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.
Summary
2fa_bot.pybind mounts during keepalive and recreate only the affected Gateway targetRoot cause
Repository sync replaces the deploy directory while the running container still holds the old bind-mounted inode. The container can therefore see an empty/stale 2FA bot, preventing authentication and leaving the API TCP socket unable to complete an IB handshake.
Impact
The fix applies to every independently configured target in
IB_GATEWAY_TARGETS_JSON; it does not merge targets or change their VM/container topology.Validation
for test_file in tests/*.sh; do bash "$test_file"; doneactionlintgit diff --check