Azure-pipelines-tasks: AzureRM Web App deployment issue : Cannot read property 'id' of undefined

[PrashanthReddyAnnedla]

We are using Deploy AzreRM Web App task for deployment. Getting below error while deploying

2016-10-12T09:36:10.2957680Z ##[debug]Processing: ##vso[task.issue type=error;]TypeError: Cannot read property 'id' of undefined
2016-10-12T09:36:10.2957680Z ##[error]TypeError: Cannot read property 'id' of undefined

Attaching the log
Error.txt

[vincent1173]

@PrashanthReddyAnnedla , please add console.log(url); console.log(headers); below azurermutil.js
and console.log(body); console.log(webAppIDDetails ); below azurermutil.js
and run the task and provide the logs. Please make sure that the changes are made in '.js' files not in '.ts' files.
'azurermutil.js' file will present in E:\agent_work\_tasks\AzureRmWebAppDeployment_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\2.0.2\
Please share the web app name too.

[nibras85]

I am getting the same issue. Very frustrating..

[PrashanthReddyAnnedla]

@vincentdass - We dont have access to the Agent machines hence cannot update the script!

I will try to do it my local agent and see if I am able to repro this issue!

[nibras85]

@vincentdass I was able to add the logging to the task in my local agent and I got the output but it has my subscription ID and other sensitive info that I can't share here... from what I gathered from the logs... I'm guessing that the API call to look up the Azure WebApp... is returning an empty array...

[vincent1173]

@nibras85 , thanks for the info. Can you replace header in azurermutil.js with
var headers = { authorization: 'Bearer '+ accessToken, 'Cache-Control': 'no-cache' };
and queue a new build/release ?

[nibras85]

@vincentdass I did. Same error.

[PrashanthReddyAnnedla]

@vincentdass ,
One more observation : Selected the slot, resource group in the task. Got the error as 404 not found, though the website exists

[vincent1173]

@PrashanthReddyAnnedla , Did you create a slot from Azure Portal ? (if Slot is not created, it throws 404 error)

If your slot name is 'Production' :
Production slot is applicable only for Azure Classic Web Deployment Task. It should not be explicitly specified as slot for AzureRM web App Deployment task. By default, it is deployed in Production slot.

Can u share the web app name and the slot name ? Please share the agent version too.

[PrashanthReddyAnnedla]

@vincentdass
I am not trying to create a new slot here, deploying to Production slot only.
I will send you the details over the mail.

[vincent1173]

@nibras85 , Can u mail the log with debug messsages ?

[nibras85]

@vincentdass please share your email address and I can share the logs with you. Thanks.

[vincent1173]

@nibras85, [email protected]

[nibras85]

@vincentdass sent. Thanks a lot.

[vincent1173]

@nibras85 , @PrashanthReddyAnnedla . It's a genuine issue and will be fixed in the upcoming deployment.

[mxa0079]

@vincentdass any workarounds? In my case, I need to automate the deployment of an ASP.NET Core app

[bryanmacfarlane]

@vincentdass - do we want to patch the task or is it fixed in 107 (rolling now)?

[vincent1173]

@bryanmacfarlane - We will patch this issue with 107. We have recently identified the different cause of issue will fix it soon .

[Ajay-MS]

@mxa0079

We have identified different cause of this issue. Need some info from you regarding issue.

1. Does webapp on which you are trying to deploy already exists?
2. Follow steps being mentioned by @vincentdass in his first reply.
3. Enable debug logs, you can enable debug logs by adding variable 'System.Debug' and set its value to 'true' and share logs at [email protected].

[mxa0079]

@Ajay-MS We are using hosted agents,so we cannot make the changes mentioned by @vincentdass (and cannot afford the time to create a dedicated agent to debug this issue) -- however, I will be glad to enable the verbose logs if this will help you.

[vincent1173]

The issue is hotfixed. If the error occurs again , please open this thread.