Duplicate volumes/issues for new resources need manual deduplication

[arcangelo7]

A bug was discovered in the container discovery process that caused duplicate volumes and issues to be created when processing new resources. While the deduplication mechanism worked correctly for existing resources, it failed to properly identify and merge containers for newly created resources.

Technical Details

The issue occurred because:

1. For existing resources, the system could traverse both incoming and outgoing part_of relationships
2. For new resources, only outgoing relationships were checked, missing potential existing containers
3. This led to the creation of duplicate volumes/issues when processing new resources that should have been linked to existing containers

Current Status

• The bug has been fixed in commit 45f285c
• The fix ensures proper container discovery for both new and existing resources
• However, duplicate volumes and issues created before the fix need to be manually merged

Required Action

A dedicated operation is needed to:

1. Identify duplicate volumes and issues in the database
2. Merge these duplicates while preserving all relationships

This cannot be automated as part of the fix since it requires careful validation of the merging process to ensure no data is lost.