Octopus: nupkg deploy to Azure Web App fails on file already exists

TL;DR

Upgrade Octopus Server to 2024.1.12875, 2024.2.9235, 2024.3.4044, or any 2024.4+ release, which contain the fix. The deployment itself succeeds and only the release bookkeeping fails, so this is safe to patch without redeploying everything.

Steps

1. Upgrade Octopus Server to 2024.1.12875, 2024.2.9235, 2024.3.4044, or any 2024.4+ release, which contain the fix. The deployment itself succeeds and only the release bookkeeping fails, so this is safe to patch without redeploying everything. Confirm the release step completes cleanly after the upgrade.

Expected: A maintainer confirms the fix shipped in specific releases.

When to use

Use this skill when you run into "Octopus: nupkg deploy to Azure Web App fails on file already exists".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 2024.1.12875, 2024.1.12875 2024.2.9235, 2024.2.9235 2024.3.4044. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue OctopusDeploy/Issues#8727 (closed): deploying a nupkg to an Azure App Service fails the release-package part with The file already exists, although the package itself deploys. A maintainer confirms the fix shipped in specific releases.

Verified resolution: Upgrade Octopus Server to 2024.1.12875, 2024.2.9235, 2024.3.4044, or any 2024.4+ release, which contain the fix. The deployment itself succeeds and only the release bookkeeping fails, so this is safe to patch without redeploying everything. Confirm the release step completes cleanly after the upgrade.

Source URL: https://github.com/OctopusDeploy/Issues/issues/8727