Add realizedstate check if CR is not ready #1262
Merged
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.
When NSX Operator restarts after vpc is created and before vpc realization check,
the NSX vpc will be loaded to cache during NSX Operator initialization even if the
realization fails.
Thus we need to check the realized state again if we detect the Namespace
CR does not have a NamespaceNetworkReady condition even if the existing vpc
in store is not changed.
This issue also exists for Subnet and StaticRoute, updated to check CR condition when
the corresponding nsx resource is not changed in createOrUpdate function.
Testing done:
Bug: 3593653