When deleting packages from the builtin package feed (Manually or due to repository retention policies) the package deletion is assumed however not checked

[danefalvo]

Prerequisites

• I have verified the problem exists in the latest version
• I have searched open and closed issues to make sure it isn't already reported
• I have written a descriptive issue title
• I have linked the original source of this report
• I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

If the account that runs the Octopus Service does not have the required access to delete a package, all indications from within the Octopus GUI will show that the Package has been removed, however the package remains and will re-appear in the Octopus GUI after the next re-index.

What I expected to happen

An alert or notice if the permissions don't exist or if the package fails to get removed.

Steps to reproduce

1. Upload a package
2. Change the permissions on one of the Package folders - if this is a default installation then:
   Navigate to C:\Octopus<Instance>\Packages\Spaces-1\feeds-builtin\PackageName -> Open Properties
3. Remove the modify property on the service account that currently runs the octopus service. There may be a number of permissions that you will need to alter (i.e. Creator Owner & Administrators).
4. Apply permissions
5. Delete the package manually from the Octopus GUI Package Repo

Screen capture

2.

3.

4.

Retention Policies

Affected versions

Octopus Server: 2020.5.3

Workarounds

Only Manually identifiable.

Links

https://octopus.zendesk.com/agent/tickets/61951