Detele blob storage error

Question

After delete a registry or component inside of the blob storage, the system show us a message error about the resource doesn't exist more but keeps appearing.

Answer 1

When you encounter an error stating that a resource doesn't exist in Azure Blob Storage after attempting to delete it, there are a few potential reasons for this issue:

1. Soft Delete Feature: If the soft delete feature is enabled for your storage account, deleted blobs are retained for a specified retention period. During this time, they may still appear in listings, but they cannot be permanently deleted until the retention period expires.
2. Caching Issues: Sometimes, the Azure portal or your application might cache the state of the resources. Refreshing the portal or clearing the cache might help in reflecting the current state of the resources.
3. Propagation Delay: After a deletion operation, there might be a slight delay before the changes are fully propagated across the Azure infrastructure. This can lead to temporary inconsistencies in the resource state.
4. Lease State: If the blob was leased at the time of deletion, the lease must be broken before the blob can be deleted. If the lease is still active, the blob may not be deleted successfully.

To resolve this issue, you can try the following steps:

• Check if soft delete is enabled and if the blob is still within the retention period.
• Refresh the Azure portal or your application to ensure you are viewing the most current state.
• Wait a few moments and check again to see if the deletion has been fully processed.
• If applicable, ensure that there are no active leases on the blob before attempting deletion again.

Answer 2

Hello @Oscar Romero,

Thanks for reaching out to Microsoft Q&A.
It sounds like you're experiencing some issues when trying to delete items in your blob storage, specifically getting an error that the resource doesn’t exist, even though it appears to still be present. This kind of issue can be frustrating, but let’s see if we can break it down.

Here are a few steps you can try:

Refresh the Blob Storage: Sometimes, the interface might not reflect the latest state. Refresh your storage account in the Azure portal to see if the item still appears.

Check for Cached Items: If you're using a caching mechanism, ensure that it is cleared up and doesn't affect the visibility of blob resources.

Diagnostic Logs: Enabling diagnostic logs can be helpful. Here’s how you do it:

• Go to the Azure portal and select Storage Accounts.
  • Choose your storage account and go to Diagnostic settings.
• Enable diagnostic logs and select the appropriate options to capture errors.
  • Analyze the logs to see if there’s more information available regarding the deletion error.

Permissions and Access: Verify that you have the necessary permissions to delete the resources. Sometimes, policies might prevent the deletion of certain items.

Retry the Deletion: After checking everything, try deleting the items again. You might also want to consider using the Azure Storage Explorer tool for a more graphical approach to managing your blobs.

https://learn.microsoft.com/en-us/rest/api/storageservices/blob-service-error-codes

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".