Cloud discovery doesn't return all configuration items (for example, VM instances) from cloud provider (for example, AWS, Azure). Log (ListNodes method) in Cloud API Trail module shows the VM information in route_result but it does not update in CMDB.

Steps to Reproduce



  1. On a Jakarta instance earlier than Jakarta Patch 2, navigate to Service Catalog > Activate Plugin, activate the Cloud Management Platform (CMP) plugin, and click Submit.

  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.

    Discovery fails.




This issue is partially fixed in Jakarta Patch 4 and Jakarta Patch 5.

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.

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:2018-03-28 05:03:22