-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
For some executions the uploaded results are not available for S3 read immediately and the cmdlet returns:
System.InvalidOperationException: The specified key does not exist. ---> Amazon.S3.AmazonS3Exception: The specified key does not exist. ---> Amazo
n.Runtime.Internal.HttpErrorResponseException: The remote server returned an error: (404) Not Found. ---> System.Net.WebException: The remote server return
ed an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at Amazon.Runtime.Internal.HttpRequest.GetResponse()
--- End of inner exception stack trace ---
at Amazon.Runtime.Internal.HttpRequest.GetResponse()
at Amazon.Runtime.Internal.HttpHandler`1.InvokeSync(IExecutionContext executionContext)
at Amazon.Runtime.Internal.RedirectHandler.InvokeSync(IExecutionContext executionContext)
at Amazon.Runtime.Internal.Unmarshaller.InvokeSync(IExecutionContext executionContext)
at Amazon.S3.Internal.AmazonS3ResponseHandler.InvokeSync(IExecutionContext executionContext)
at Amazon.Runtime.Internal.ErrorHandler.InvokeSync(IExecutionContext executionContext)
--- End of inner exception stack trace ---
at Amazon.PowerShell.Utils.ProgressRunner.Run(Action action, ProgressTracker tracker)
at Amazon.PowerShell.Utils.ProgressRunner.SafeRun(Action action, ProgressTracker tracker)
--- End of inner exception stack trace ---
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
Probably in these cases we need to add an extra wait to let enough time for S3 to make the results available for read after the uploads.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels