AWS/Azure Cloud Discovery doesn't discover VM due to Hardware type pattern all failed with error: cmdb_ci_compute_template cannot be created since there are no attributes definedIssue AWS/Azure Cloud Discovery doesn't discover VM. For example in case of AWS; AWS VMs are discovered via pattern "Amazon AWS - Virtual Server (LP)". Following sn_pattern_trigger_rule, this pattern is launched by "Amazon AWS - Hardware Type (LP)". However "Amazon AWS - Hardware Type (LP)" pattern fails with error: cmdb_ci_compute_template cannot be created since there are no attributes definedCausePlease check: 1> if below system exists: sn_itom_pattern.use a single hardware type true 2> if the main CI type for pattern "Amazon AWS - Hardware Type (LP)" is cmdb_ci_compute_template If above are met, then we can confirm the issue is caused by incomplete configuration of "Migrating to a new hardware type model" steps.ResolutionPlease review KB below to determine if you would like to migrate to a new hardware type model: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955939 -If you don't intend to proceed with the migration, please set system property sn_itom_pattern.use a single hardware type to false. -If you would like to complete the migration, please follow the Instructions in the KB. Please note the fix script in the KB won't work if Cloud Provision and Governance or Cloud Insights is activated. We don't recommend the migration if any of these two plugins is used. However if you still want to proceed with the plugins activated, you may review the fix script, remove the conditions that checks on these plugins then run it.