Delete Stale Hardware Type Relationships with Virtual Machines in Service Graph ConnectorsSummaryThis article outlines the steps to identify and remove stale Hardware Type relationships associated with Virtual Machines (VMs) in your CMDB. Using a provided update set and one-time fix scripts, this solution ensures that each VM maintains a single, accurate Hardware Type relationship. Issue In some instances, multiple cmdb_rel_ci relationship records may exist between a single Virtual Machine (VM) and a Hardware Type CI. This typically occurs due to VM resizing operations. These redundant relationships may lead to inaccurate CMDB data and must be cleaned up to ensure data integrity. Additional Information This fix is a one-time cleanup. No recurring job is necessary. In the new load, the SGC job from the mentioned release automatically checks for stale relationships and deletes outdated relationships between Hardware Templates and VMs.ReleaseThe following Service Graph Connector versions and higher: SR - CMDB - Service Graph Connector for AWS v2.10SR - CMDB - Service Graph Connector for Google Cloud v1.9SR - CMDB - Service Graph Connector for Microsoft Azure v1.12 InstructionsTo resolve the issue, apply the provided update set and run the one-time fix script specific to your cloud connector. The fix script will: Download the Update Set [Attach the update set here for download]Navigate to System Update Sets > Retrieved Update Sets.Import and commit the provided update set.Run the One-Time Fix ScriptDepending on your connector, run the appropriate fix script: GCP Connector: Remove stale Hardware Type rel for GCPAWS Connector: Remove stale Hardware Type rel for AWSAzure Connector: Remove stale Hardware Type rel for Azure Navigate to System Definition > Fix Scripts and execute the relevant script. Fix script details Query the sys_object_source table to identify VMs created for the specified Discovery Source.Search for multiple cmdb_rel_ci relationships between each VM and its Hardware Type.Identify and remove older, stale relationship and retaining only the most recent or valid one.The next full load of the SGC will recreate the correct relationship if needed, ensuring only one active relationship exists for each VM.