You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently a "local" installation of Turbinia will accept a GoogleCloudDisk processing request even if it won't be able to process it and all Tasks will fail with an error similar to Task Result was auto-closed from task executor on <worker name> likely due to previous failures. Previous status: [FileArtifactExtractionTask Task failed with exception: [name 'google_cloud' is not defined]]. It would be nice if either the client rejected this immediately or the API server rejected it when the request was submitted. Previously turbiniactl was able to load the config and determine if the server was a cloud instance or not, but the turbinia-client doesn't necessarily have access to this, so it might need to be done at the API server.
What would this feature improve or what problem would it solve?
This will be much easier for users to understand because a) they see it earlier when the request is made and b) the error can be much clearer as to what the real problem is.
What alternatives have you considered?
n/a
The text was updated successfully, but these errors were encountered:
What is the feature you are proposing?
Currently a "local" installation of Turbinia will accept a GoogleCloudDisk processing request even if it won't be able to process it and all Tasks will fail with an error similar to
Task Result was auto-closed from task executor on <worker name> likely due to previous failures. Previous status: [FileArtifactExtractionTask Task failed with exception: [name 'google_cloud' is not defined]]
. It would be nice if either the client rejected this immediately or the API server rejected it when the request was submitted. Previouslyturbiniactl
was able to load the config and determine if the server was a cloud instance or not, but theturbinia-client
doesn't necessarily have access to this, so it might need to be done at the API server.What would this feature improve or what problem would it solve?
This will be much easier for users to understand because a) they see it earlier when the request is made and b) the error can be much clearer as to what the real problem is.
What alternatives have you considered?
n/a
The text was updated successfully, but these errors were encountered: