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



  1. On an early Jakarta instance navigate to Service Catalog > Activate Plugin and activate the Cloud Management Platform (CMP) plugin.

  2. 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.

  3. Navigate to Discovery > Discovery Schedule > Quick Discovery and run discovery.

  4. Upgrade the instance to Jakarta Patch 2 or Jakarta Patch 3.

    For more information, see the documentation topic Upgrade your instance.

  5. Add a new service account.

  6. 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:

  1. Set the system property glide.upgrade.optimize.in_family (via sys_properties.list) to false.
  2. Activate the Cloud Management Core and Cloud Management plugins.
  3. 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

Seen In

There is no data to report.

Fixed In

Jakarta Patch 4
Jakarta Patch 5
Jakarta Patch 6

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:38:46