Discovery Pattern Extension doesn't create CI.

[Au_an]

Hi everyone,

I've created a custom pattern extension linked to the already existing Linux Server pattern in order to discover OVM virtual machines and create new entries in a custom table (ci class type) also created by me, child of Virtual Machine Instance class.

The discovery log reports the creation step as completed and VMs are being discovered, but the table is still empty. I used "Transform Table" to create the entries into the custom table, with source table the one in which I stored all the VMs during the pattern execution and target table the custom table.

Did I missed some steps? Is there anything else to do when creating a custom class in order to enable discovery to create an entry?

Moreover, I don't know if it can help, but when I try to search that custom class into filter navigator, it doesn't appear. I need to access it by using its full name.list. But I can see it in CI Class Manager.

Thank you very much for your help!

[Au_an]

Yes, already added as shown below

[Kieren]

Hi @Au_an 
I came across this while trying to fix a similar issue.  Mine was due to creating a new CI class and pattern in one instance, and migrating it to another instance.
The pattern I created works in the source instance but not the one I migrated to.

I found that the target instance was missing a cmdb_class_info record for the new class I created.  Migrating this record from the source instance fixed my issue.
If you've only been working in a single instance, perhaps just check if there is a cmdb_class_info record for your new class, and if there isnt create one.

[Community Alums]

I know this is old, but we just experienced the same problem, and all of the suggestions here did not work.  What finally did work was actually restarting the MID server - just synchronizing the patterns with MID was not sufficient.