-
Notifications
You must be signed in to change notification settings - Fork 218
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
Does not return after logging "Error identifying update scenario." #599
Comments
Hello @takuhiro, Thank you for this query. An ideal thing to do would be to re-create these objects. Now there are two empty variables here:
The expectation here is that the re-installation would self-heal the deployment and the daemonset such that in the next iteration version information can be properly retrieved. |
@ntap-arorar Thank you for the detailed answer. I understood the logic when In our case, the complete error message was this. (I'm sorry I should have include the context first.)
The error |
I believe there is a scope of making this logic more resilient to unintended re-installs due to temporary issues (false positive) in the Kubernetes environment. This does depend on the error type being returned otherwise the Operator may miss on healing real Trident installations that are in bad shape. |
I agree that the error should be handled by the error type. If the error type represents temporary issues, the controller can skip re-installation because the error would be resolved soon in the next iteration. |
This issue is fixed with commit bf43f8 and is included in the Trident 21.10.0 release. |
Describe the bug
We found the code that does not return after receiving error.
https://github.com/NetApp/trident/blob/stable/v21.04/operator/controllers/orchestrator/controller.go#L1177-L1184
In that case
currentInstalledTridentVersion
andtridentK8sConfigVersion
are empty, but these variables are used in the following code.I'm not sure this is a bug, but if not returning after error, the variables might be used unexpectedly.
Environment
The text was updated successfully, but these errors were encountered: