pacCLI failure on deploying solution to target dataverse

[Vaibhav-Raj10]

We are using YAML pipeline which has a solution import step wherein we're deploying a dll onto dataverse . For import/deploy purposes, we are using pacCLI package deploy. In this particular step, the solution is being deployed to an org for the purpose of integration test. But before the tests can begin, the deploy step fails with a vague message. Here's the pacCLI command:

C:__w_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\2.0.77\bin\pac\tools\pac.exe package deploy -env https://aurorabapenv35cea.crm10.dynamics.com/ -p C:__w\1\BuiltSolutionArtifacts\package\PSPackage.dll -lf C:__w\1\a\DeployPackage\deploy-package\PSPackage_20240904085339.log -c False

Here's the error screenshot:

In detailed logs I can see:

2024-09-05T08:28:30.8059338Z Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : ************ CommunicationException - ImportSolutionAsync : msdyn_ProjectServiceCore_Patch - Executing Request for ImportSolutionAsyncRequest :  |=> The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
2024-09-05T08:28:30.8059912Z Source	: mscorlib
2024-09-05T08:28:30.8060812Z Method	: HandleReturnMessage
2024-09-05T08:28:30.8061905Z Date	: 9/5/2024
2024-09-05T08:28:30.8062292Z Time	: 7:28:12 AM
2024-09-05T08:28:30.8063521Z Error	: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
2024-09-05T08:28:30.8064358Z Stack Trace	: Server stack trace: 
2024-09-05T08:28:30.8065711Z    at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
2024-09-05T08:28:30.8066657Z    at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
2024-09-05T08:28:30.8067419Z    at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
2024-09-05T08:28:30.8068563Z    at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
2024-09-05T08:28:30.8069633Z    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
2024-09-05T08:28:30.8070747Z    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
2024-09-05T08:28:30.8071071Z    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
2024-09-05T08:28:30.8071914Z 
2024-09-05T08:28:30.8072915Z Exception rethrown at [0]: 
2024-09-05T08:28:30.8073775Z    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
2024-09-05T08:28:30.8074865Z    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
2024-09-05T08:28:30.8075325Z    at Microsoft.Xrm.Sdk.IOrganizationService.Execute(OrganizationRequest request)
2024-09-05T08:28:30.8076835Z    at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient`1.ExecuteAction[TResult](Func`1 action)
2024-09-05T08:28:30.8077611Z    at Microsoft.Xrm.Tooling.Connector.CrmServiceClient.CrmCommand_Execute(OrganizationRequest req, String errorStringCheck)
2024-09-05T08:28:30.8078821Z ======================================================================================================================
2024-09-05T08:28:30.8079822Z Inner Exception Level 1	: 
2024-09-05T08:28:30.8080919Z Source	: System
2024-09-05T08:28:30.8082370Z Method	: GetResponse
2024-09-05T08:28:30.8083362Z Date	: 9/5/2024
2024-09-05T08:28:30.8084349Z Time	: 7:28:12 AM
2024-09-05T08:28:30.8085331Z Error	: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
2024-09-05T08:28:30.8085852Z Stack Trace	: at System.Net.HttpWebRequest.GetResponse()
2024-09-05T08:28:30.8087526Z    at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)


2024-09-05T08:28:30.9577145Z PackageDeployVerb Information: 8 : Message: msdyn_ProjectServiceCore_Patch - Error getting data for Import job. ImportID:0031670b-bd22-4600-8a7c-41272b98139c
2024-09-05T08:28:30.9578565Z PackageDeployVerb Error: 2 : Message: msdyn_ProjectServiceCore_Patch - Import Job Exceeded timeout threshold of 60 minuets 
2024-09-05T08:28:30.9579141Z ID:0031670b-bd22-4600-8a7c-41272b98139c
2024-09-05T08:28:30.9580073Z PackageDeployVerb Information: 8 : Message: Completed Processing Of Solution: Project(msdyn_ProjectServiceCore_Patch), Version: 1.0.108.78, PackageVersion: 9.1, Duration: 01:02:10.872, Result: Error

On multiple attempts at re-run of the pipeline, this stage passes. So, it appears to be an intermittent issue. But it is too frequent to ignore.

I am being told that this could be an issue with solution import size. Or could be an issue with log file trailing. Can someone help here and point me to the potential cause(s) of the deploy failure. I tried searching for similar issue but couldn't find any post with relevant information.

[Vaibhav-Raj10]

bump