-
Notifications
You must be signed in to change notification settings - Fork 93
Recover Full Site Before Reconfiguring Rotuer #2519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
c-kruse
wants to merge
1
commit into
skupperproject:main
Choose a base branch
from
c-kruse:fix-site-recovery-stability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Filter attached connector recovery by target site namespace.
checkAttachedConnectorapplies the object toconnector.Spec.SiteNamespace, so this recovery filter can skip externally-namespaced attached connectors that target a controlled site. Use the target site namespace for the control check.🐛 Proposed fix
for _, connector := range c.attachedConnectorWatcher.List() { - if !c.namespaces.isControlled(connector.Namespace) { + if !c.namespaces.isControlled(connector.Spec.SiteNamespace) { continue }📝 Committable suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TestRecoveryPreservesRouterBridgeConfigmight not catch that because default test config hasrequireExplicitControl=false, soisControlled("attached")still passes I believe.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 1127
🏁 Script executed:
Length of output: 3644
@AryanP123, you're right — with the default test config,Config.requireExplicitControl()evaluates tofalse(sinceWatchingAllNamespaces()is likely true andRequireExplicitControlis unset), soNamespaceConfig.isControlledfalls through toreturn trueregardless of which namespace is checked. That meansTestRecoveryPreservesRouterBridgeConfigwouldn't distinguish between checkingconnector.Namespacevsconnector.Spec.SiteNamespace— it's not exercising the namespace-scoping logic at all.The original correctness concern about using
connector.Spec.SiteNamespace(to match whatcheckAttachedConnectoractually operates on) still stands independently of test coverage. If you want to guard against regressions here, a follow-up test could setRequireExplicitControl: true(or watch a specific namespace) and create anAttachedConnectorwhose.Namespacediffers from.Spec.SiteNamespace, then assert recovery still applies it when the site namespace is controlled. Happy to help sketch that out if useful, otherwise this can be tracked as a known test gap.