# Delete hanging backup **URL:** \ **Category:** Get Help\ **Tags:** awx\ **Created:** [March 21, 2025, 8:49am UTC](https://forum.ansible.com/t/delete-hanging-backup/41175 "2025-03-21T08:49:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ildjarn](https://avatars.discourse-cdn.com/v4/letter/i/8491ac/32.png) [@ildjarn](https://forum.ansible.com/u/ildjarn)\ **Post date:** [March 21, 2025, 8:49am UTC](https://forum.ansible.com/t/delete-hanging-backup/41175/1 "2025-03-21T08:49:23Z")
I am slowly upgrading all the AWX deployments in my company. Basically what I’m doing is: - Save all secrets from the old deployment - Delete old namespace - Redeploy using my own yamls This works great, but for one environment I run into a problem doing step 2: Deleting the old namespace. The namespace stays in ‘terminating’ status. When searching for reasons I found out that there’s an AWXBackup object that can’t be deleted. How can I check the log of the backup to see what the problem is? My guess is that it’s trying to backup to a directory that does not exist (anymore?). I found [kubectl delete stuck - what to do and why this happen| Devops Junction](https://www.middlewareinventory.com/blog/kubectl-delete-stuck-what-to-do/) which says ‘Just delete the finalizers’, but I’m hesitant to do that. `kubectl describe awxbackup 'mybackup' -n myns` doesn’t show any errors or events, and `kubectl logs awxbackup/mybackup -n myns` says `error: no kind "AWXBackup" is registered for version "awx.ansible.com/v1beta1" in scheme "pkg/scheme/scheme.go:28"`, probably because the backup type is namespace bound. ---
**Author:** ![ildjarn](https://avatars.discourse-cdn.com/v4/letter/i/8491ac/32.png) [@ildjarn](https://forum.ansible.com/u/ildjarn)\ **Post date:** [March 26, 2025, 7:19am UTC](https://forum.ansible.com/t/delete-hanging-backup/41175/2 "2025-03-26T07:19:09Z")
I’ve decided to just delete the finalizers in the backup object, and the namespace is gone now. It’s a test environment anyway.