[Issue] Azd says app successfully deployed, App service logs say it didn't

[pamelafox]

• [ ] Make sure you've installed the latest version using instructions in the wiki

Output from azd version

azd version 1.9.3 (commit e1624330dcc7dde440ecc1eda06aac40e68aa0a3)

Describe the bug

azd said my app deployed successfully:

Deploying services (azd deploy)

  (✓) Done: Deploying service backend
  - Endpoint: https://app-backend-ixehwdxj5j4oe.azurewebsites.net/

SUCCESS: Your up workflow to provision and deploy to Azure completed in 29 minutes 42 seconds.

However, when I check App Service deployment logs, I see the most recent deployment was a failure:

To Reproduce

I find that App Service deployments fail fairly often so perhaps if you deploy enough times, you can reproduce? Or maybe you can get deployment every time by putting a bad package name in requirements.txt, that might fail the Oryx build step.

Expected behavior

I think azd should indicate that the deployment failed.

[weikanglim]

Similar to https://github.com/microsoft/Oryx/issues/1956

@pamelafox Historically, azd has always been using the ZipDeploy API which would not have reported failures after the upload operation completes, such as the post-upload remote build that you're seeing.

We did merge a change last week #3965 (in daily build but unreleased yet) that uptakes the new ARM deployment status API for Linux Web Apps that will track the build operation as well. This should address these types of issues with Linux on App Service.

[pamelafox]

Ah okay, I wasn't sure if deployment status API support was currently released. I can monitor the situation once that's released.

[jongio]

@pamelafox Could you try again with latest azd?

[hemarina]

Checked with @pamelafox that this issue is not seen.