E2E: check for uninstall pod init container successfully completed #113
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
...instead of pod phase "running" as we've observed sporadic failures where the pod phase is still "pending" even though the init container successfully completed. Also the operator log reported that the associated daemonset was deleted. So uninstall worked correctly. The pod status is cached in the E2E via an informer so it's likely the phase update didn't occur b/c the pod was deleted or it hadn't occurred yet. Signed-off-by: Tom Pantelis <[email protected]>
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.
...instead of pod phase "running" as we've observed sporadic failures where the pod phase is still "pending" even though the init container successfully completed. Also the operator log reported that the associated daemonset was deleted. So uninstall worked correctly. The pod status is cached in the E2E via an informer so it's likely the phase update didn't occur b/c the pod was deleted or it hadn't occurred yet.