Cloud Discovery does not return all configuration items, like VM instances, from cloud provider (i.e.: AWS, Azure). The ListNodes method log in the Cloud API Trail module shows the VM information in route_result but it does not update in CMDB.
Steps to Reproduce
On an early Jakarta instance navigate to Service Catalog > Activate Plugin and activate the Cloud Management Platform (CMP) plugin.
Add a new service account by navigating to Cloud Management > Cloud Infrastructure > Service Accounts and clicking New.
For more information, see the product documentation topic Create a service account for Cloud Management.
Navigate to Discovery > Discovery Schedule > Quick Discovery and run discovery.
Upgrade the instance to Jakarta Patch 2 or Jakarta Patch 3.
For more information, see the documentation topic Upgrade your instance.
Add a new service account.
Run Discovery. Observe the process fails.
This issue is partially fixed in Jakarta Patch 4-5, and definitely fixed in Jakarta Patch 6 and later releases.
Workaround for Jakarta Patch 4:
- Set the system property glide.upgrade.optimize.in_family (via sys_properties.list) to false.
- Activate the Cloud Management Core and Cloud Management plugins.
- Set the property glide.upgrade.optimize.in_family to true.
NOTE: The above steps require SN 'maint' access and subscription confirmation before applied on production instances. As per documentation "Cloud Management is available as a separate subscription from the rest of the platform. You must also request activation fromServiceNow personnel."
Workaround for Jakarta Patch 5:
- Try reactivating the Cloud Management Core and Cloud Management plugins.
Related Problem: PRB1182010