To Reproduce Steps to reproduce the behavior:

1. Prepare FFU on overcloud deployment from a previous version that includes the `_DEFAULT_` volume type
2. Create one volume in any project other than admin with volume type `_DEFAULT_`
3. Run overcloud upgrade
4. Overcloud upgrade fails to delete the `_DEFAULT_` volume because a volume exists of this type

Expected behavior

• Cleanup task should check volumes in all projects and filter by type

Bug impact

• Breaks overcloud upgrade

Known workaround

• Manually delete existing volumes using the `_DEFAULT_` volume type

Additional context

• See attached case where the customer ran into this issue