Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Status 'cmdb_ci_cloud_database' does not get updated in CMP portal - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Status 'cmdb_ci_cloud_database' does not get updated in CMP portal
KB0813229

Status 'cmdb_ci_cloud_database' does not get updated in CMP portal


632 Views Last updated : Apr 8, 2025 public Copy Permalink
KB Summary by Now Assist

Description

The 'cmdb_ci_cloud_database' status does not get updated after the Stack provisioning, even through the respective DataBase instance is up and running.

Steps to Reproduce

  1. Navigate to Cloud Admin Portal
  2. Create a new Cloud Catalog Item, Source should be "Cloud Template" and Template Type "CloudFormation Template"
  3. Use the attached template "AWS RDS MySql Template.txt" to create the Cloud Template. Save the Cloud Template and Activate it
  4. Click the "Active" checkbox to mark your Cloud Catalog Item as Active.
  5. Navigate to Cloud User Portal and launch a stack using the above created Cloud Catalog Item
  6. Upon successful provision click on "View Stack Details. Notice for the DBInstance (cmdb_ci_cloud_instance) captured, the status is empty, not updated and greyed out, but on AWS the DataBase instance shows up and running.

Workaround

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

As the current design does not support Discovery for this type of CI, download and apply the attached update set AWS cloud database status in a dev instance to test if it can be an acceptable solution.


Related Problem: PRB1376212

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.