Windows Discovery Pattern Error - CI Reclassification not allowed

[SamJoe]

Hi,

On many Windows Servers discovery pattern logs I see this error which is preventing the server to be discovered. I have already added/enabled the following IRE properties to true -

glide.identification_engine.update_without_switch_enabled, glide.class.switch.enabled

but still getting the error - CI Reclassification not allowed from class: [cmdb_ci_iscsi_disk] to [cmdb_ci_storage_device]

Has anyone seen this before and can you help how to overcome this?

Also, it discoveres fine if I delete the CI and re-discover it.

Thanks

-S

[Selva Arun]

Hi S,

Have you gone through Discovery error CI Reclassification not allowed - Support and Troubleshooting article?

In Summary:

Issue

The error "CI Reclassification not allowed" occurs during discovery when the system attempts to reclassify a CI from one class to another (e.g., [cmdb_ci_msd] to [cmdb_ci_storage_node_element]). If automatic reclassification is disabled, the system blocks the reclassification and generates a reclassification task.

---

Cause

The error arises because the Identification and Reconciliation Engine (IRE) restricts class upgrades, downgrades, or switches unless explicitly allowed by system properties or payload flags.

---

Resolution Options

1. System Properties
   Enable the following properties to allow class changes:
   • glide.class.upgrade.enabled
   • glide.class.downgrade.enabled
   • glide.class.switch.enabled
   • glide.identification_engine.update_without_switch_enabled
   • glide.identification_engine.update_without_downgrade_enabled
   • glide.identification_engine.update_without_upgrade_enabled
2. Reclassification Task
   • Navigate to Configuration > Identification/Reconciliation > Reclassification.
   • Review the payload and adjust it to avoid reclassification if possible.
3. Payload Flags
   Add the following flags to the payload to temporarily override IRE restrictions:
   • classUpgrade, classDowngrade, classSwitch
   • Example:
     json

     Copy Code

     { items: [{className: "cmdb_ci_server", classUpgrade: true, classDowngrade: true, classSwitch: true, values: {name: "linux123"}}]}
   Alternatively, use these flags to allow updates without class changes:
   • updateWithoutUpgrade, updateWithoutDowngrade, updateWithoutSwitch
   • Example:
     json

     Copy Code

     { items: [{className: "cmdb_ci_server", values: {name: "linux123"}, "settings": {"updateWithoutSwitch": "true"}}]}
4. Pre/Post-Processing Scripts
   Adjust the payload in discovery pre/post-processing scripts or transform scripts to align with the existing CI class.

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva Arun

[Doci1]

Hi @SamJoe , i had the same issue, only what I could is to delete related [cmdb_ci_iscsi_disk] and re-run the discovery. Seems to me that it is a problem of the Windows-OS pattern, but as on the intial run all was OK and I am not subject matter expert (of Windows servers), we sticked to delete incorrect iscsi disks