Notifications

78 views

Description

If we try to change class name for bulk CIs (more than 30) from the UI, then it may lead to cancellation of the transaction as long running.
This cancellation leading to loss of few records that are being reclassified when the transaction is cancelled.

Steps to Reproduce

  1. Take a count of the total number of CIs you have in the two classes.
  2. Navigate to the list of the CIs you want to change their class. 
  3. Right click on the column heading 'Class'.
  4. Select 'Update All'.
  5. Click 'Ok' to confirm that you want to reclassify the CIs.
  6. Input the new class
  7. Click 'Update' to save the change.
  8. Take a count of the total number of CIs you have in the two classes again and compare it to the first count.

One or more CIs are missing.

Workaround

This is Fixed in the London release and later, so please upgrade to solve this issue. Transaction Quota Rules and Cancellations are now prevented from aborting the class change process.

This was much more likely to happen in Jakarta and Kingston due to a slow-down caused by the TPP migration of the CMDB, and was the table where all reported timeouts occurred. This was also fixed in London, however the Known Error article provides a potential workaround for Jakarta or Kingston to speed up the updates to reduce the chance of them timing out:
KB0681177 - PRB1258222 Unnecessary updates during cmdb_ci class change from TPP change


Related Problem: PRB1242353

Seen In

There is no data to report.

Fixed In

London

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-24 12:20:58
Published:2019-02-27