[cherry-pick]Fix Subnet update error detection (#991) #1010
Conversation
This file contains 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
Operator modifies the existing Subnet in store before updating the NSX Subnet, which results in the next reconcile will find the updated Subnet already in store, skip the update, and overwrite the Status as Ready. This PR uses a copy when updating the Subnet to avoid this issue. Signed-off-by: Yanjun Zhou <yanjun.zhou@broadcom.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## v4.2.0 #1010 +/- ##
==========================================
+ Coverage 74.79% 74.90% +0.10%
==========================================
Files 118 118
Lines 16383 16377 -6
==========================================
+ Hits 12254 12267 +13
+ Misses 3358 3343 -15
+ Partials 771 767 -4
|
dantingl
approved these changes
Jan 17, 2025
TaoZou1
approved these changes
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Operator modifies the existing Subnet in store before updating the NSX Subnet, which results in the next reconcile will find the updated Subnet already in store, skip the update, and overwrite the Status as Ready. This PR uses a copy when updating the Subnet to avoid this issue.