Azure ML Pipeline suddenly fails (500 internal error)

Timbus, Calin 15

I have a pipeline that I have been running successfully for the last 2 months.

Now, one of the jobs runs successfully, I am checking the logs, but when it reaches the final steps I get: Finalizing ... Finalizing ... Finalizing ...

Failed to execute command group with error Docker container `5b5f21c26f5948a293ec4e7d4e8bd542-lifecycler` failed with status code `1`. Service 'HOSTTOOLS_CAPABILITY' returned capability end response with code: Response { code: "500", error: Some(Error { code: "TerminationError", message: "hosttools process exit unexpectedly with code: Some(1)", target: "hosttools-capability", node_info: None, category: SystemError, error_details: [], inner_error: None }) } How can I solve this issue?

YutongTie-MSFT 53,321 Reputation points

2023-04-26T20:27:51.96+00:00

Hello @Timbus, Calin Thanks for reporting this issue, we have escalated this error message to product team, will let you know once we have any update.
YutongTie-MSFT 53,321 Reputation points

2023-04-26T20:45:29.7266667+00:00

Hello @Timbus, Calin May I know the runID for your failure run? It's essential for the error debugging. Thanks.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Timbus, Calin 15 Reputation points

2023-04-27T06:52:29.6233333+00:00

I can confirm that the next two pipeline submissions have worked properly, but I didn't do anything different, just resubmitted the jobs; this is the one that yielded the error : 7ad7d7ad-9d2c-46e1-8b20-ce34efde8d74
Timbus, Calin 15 Reputation points

2023-04-27T11:06:09.3433333+00:00

Hello again, this is the name of the job: 7ad7d7ad-9d2c-46e1-8b20-ce34efde8d74
YutongTie-MSFT 53,321 Reputation points

2023-05-03T06:17:08.9233333+00:00

Thank you, I have forwarded it to product team for investigation.

Share via

Azure ML Pipeline suddenly fails (500 internal error)

Your answer