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
T5941: Migration policy delete orphaned interface policy #2890
Conversation
We can get orphaned interface policy when the policy name was removed from the interface but the node `policy` still attached to the interface For exmaple we have orphaned node policy on interface: ``` set interfaces bonding bond0 vif 995 policy ``` This causes of incorrect migration and we do not see VLANs on the bonding interface after update. Delete policy from all interfaces if policy does not exist
I think it would be cleaner to just remove these lines from the migrator:
It will still iterate and remove the |
I though about it and even tested before any change, looks like also safe solution |
@Mergifyio backport sagitta |
✅ Backports have been created
|
Change Summary
We can get an orphaned interface policy when the policy name is removed from the interface, but the node
policy
is still attached to the interface.For example we have orphaned node policy on an interface:
This causes of incorrect migration and we do not see VLANs on the bonding interface after update.
Delete policy from all interfaces if the policy does not exist.
Types of changes
Related Task(s)
Related PR(s)
The similar PR #2892
Component(s) name
Proposed changes
How to test
To reproduce:
After update, we do not have interface
bond0.995
but it is present in the /config/config.boot:Example:
Show interface before fix (do not see bond0.995):
Smoketest result
Checklist: