Owls 93071 - Display correct readyReplicas and server state when domain serverStartPolicy switched to NEVER #2578
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.
The incorrect readyReplicas was because the status update fiber was using a stale DPI cache for the list of ready pods. With this change, the StatusUpdate step that runs periodically makes use of the DPI cached in the
DomainProcessorImpl
instead of DPI passed when scheduling the domain status updating.The change also deletes the server pod from DPI when the pod is not found during a list operation and is fully deleted. The server state is displayed as SHUTTING_DOWN when the pod is being deleted and SHUTDOWN after the pod is deleted.
Added unit test to verify the changed behavior. The integration test results are at - https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/6762/