Linux Server Discovery issues since Zurich upgrade with cmdb_ci_lvm_pool_member

[Mercedes Pons 1]

Hello,  I hope someone can help with some issues I'm facing with Linux Discovery since Zurich upgrade one month ago.

Discovery of Linux shows Classified, but with this message:

"CI Pattern completed but failed some post-processing steps, Pattern name: Linux Server, To Check Pattern Log Press Here"  and when I review the Pattern log, this is the message:

2025-12-18 05:01:59: MISSING_MATCHING_ATTRIBUTES:
In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_lvm_pool_member]. Add these input values in payload item '{"className":"cmdb_ci_lvm_pool_member","values":{"discovery_source":"ServiceNow","install_status":"1","name":"/dev/mapper/datavg-lv_opt","end_offset":"1048567808","start_offset":"0","extent_type":"linear","sys_class_name":"cmdb_ci_lvm_pool_member"},"internal_id":"6a7baacbc57d7698309124b3d35ac6ef","sys_object_source_info":{},"settings":{},"sys_ire_info":{},"display_values":{}}'

I found that [cmdb_ci_lvm_pool_member] didn't have any Identifier Entry, and I don't seem to find the right criterion for this class.  Anyone facing this issue or any idea on how to solve it?

Any help will be appreciated with LVM pool member class Identifiers and Relationships and maybe this could help resolve the Discovery issue with Linux Servers.

Thank you

[Matthew_13 · Accepted solution]

@Mercedes Pons 1  - 

You’re not alone—this started showing up after the Zurich upgrade in ServiceNow.

Discovery is working, but IRE can’t identify cmdb_ci_lvm_pool_member because that class has no identifier rule, so post-processing fails. It’s not a credential or probe issue—just stricter IRE validation.

Most teams fixx it by adding a simple identifier for example, name plus parent, excluding that class if it’s not needed, or applying the latest Zurich patch where this is addressed.

Thumbs up if this helps you. Thanks!

[Mercedes Pons 1]

Thank you Matthew_13

In case it's useful in the future, I ended up defining the following Identifiers for cmdb_ci_lvm_pool_member (I had to try different options, and this is the one that worked)

Name with priority 100

Pool with priority 150

After that, I ran Discovery and the issue is gone.