Blob removal fails when deleting group
### Summary When deleting a group the sidekiq jobs fail repeatedly with an undefined method error. ### Steps to reproduce 1. Delete a group that has issues with images (I assume anything stored in blob storage will do) 2. Look at the background jobs ![Screenshot_2023-02-09_at_10.21.55](/uploads/300e0454025bfb87f03c9ba660fc10d5/Screenshot_2023-02-09_at_10.21.55.png) 3. These jobs will actually fail at some point and the files appear to still be in blob storage. ### What is the current _bug_ behavior? The errors are shown in the sidekiq browser thing and from what I can tell the blobs aren't removed from storage. ### What is the expected _correct_ behavior? That the error isn't shown and the blob is actually removed. ### Relevant logs and/or screenshots `NoMethodError: undefined method` delete_object' for #[Fog::Storage::AzureRM::Real:0x0000791c3c63d630](fog::Storage::AzureRM::Real:0x0000791c3c63d630) Did you mean? delete_object_url\` ### Output of checks #### Results of GitLab environment info This is on gitlab self-host 15.8.1 deployed on k8s with the gitlab operator. We run this on AKS and use Azure Blob Storage. <details> <summary>Expand for output related to GitLab environment info</summary> <pre>(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)</pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre>(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)</pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->
issue