Bug: Failed Successful Deployment - Error Handling AzureFunctionAppV1

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: AzureFunctionAppV1

Environment

Azure Pipelines

• Account: lostgolfballs
• Project Name: www.lostgolfballs.com
• BuildId: releaseId=1101

Issue Description

Upon running a AzureFunction Task with a zip file, I anticipate that I update an existing function app with the new package files.

Instead, I get a blue screen that looks like:

If I re-run the release, I get my function loading successfully after the task completes.

Task logs

Got service connection details for Azure App Service:'MY_SERVICE'
2019-09-26T19:38:57.8311929Z Updating App Service Application settings. Data: {"WEBSITE_RUN_FROM_PACKAGE":"1"}
2019-09-26T19:38:57.8312354Z Deleting App Service Application settings. Data: ["WEBSITE_RUN_FROM_ZIP"]
2019-09-26T19:39:01.7703054Z Package deployment using ZIP Deploy initiated.
2019-09-26T19:39:22.8310452Z Successfully deployed web package to App Service.
2019-09-26T19:39:28.6247890Z Successfully updated App Service configuration details
2019-09-26T19:39:28.9075674Z App Service Application URL: MY_SERVICE_URL

Other Information:

When it successfully fails, the resulting app content looks like:

Contents of Web.config:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name = "Site Unavailable" stopProcessing = "true">
                    <match url = ".*" />
                    <action type = "CustomResponse" statusCode = "503" subStatusCode = "0" statusReason = "Site Unavailable" statusDescription = "Could not download zip" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

Contents of FAILED TO INITIALIZE RUN FROM PACKAGE.txt:

Run From Package Initialization failed.

[damienwebdev]

Turns out, the bug is due to the task running as Zip Deploy but still setting WEBSITE_RUN_FROM_PACKAGE=1.

If I manually remove the WEBSITE_RUN_FROM_PACKAGE this is fixed.

[HansOlavS]

@damienwebdev I experienced the exact same issue today. I’ve been stuck for 4 hours trying to figure out why a newly created Azure Functions app wouldn’t get deployed correctly. After setting the runtime to ~2 (the newly created app has ~3 as default) then zipdeploy started working for me!