"Synchronize with MID Servers" made a discovery OOB pattern unusable

[Au_an]

Hi all, first of all thank you for opening the post.

I was working on a feature for Linux Server OOB pattern (DEV instance) in order to add a customized step for OVM Virtual Machines discovery, which is not implemented in the default OOB pattern.

So I created a shared library and added it into the Extension Section (I did not modify the main "discovery" pattern in the Identification Section) but while testing the entire Linux Server pattern it gave me a "Identification Engine: Discovery status is FAILURE, Identification sections in pattern failed: section: discovery, error: Relation and/or reference table xxx is not a known CI Type." kind of error, from a step in the custom extension.

So I changed some steps in the extension, but it gave still the same error.

Searching here in the community I found different posts that suggested to always sync with mid servers when doing edits in the patterns in order to be sure that mid server is running the latest version of that pattern. So I did it by selecting the pattern in the table > Actions on selected rows lookup > Synchronize with MID Servers. After that, returning in the Linux Server pattern, all extensions disappeared, both the one created by me and those already there, and running the pattern started giving the error "Relation and/or reference table cmdb_fc_initiator is not a known CI Type. Check the discovery logs for more details." from the main discovery pattern, even though I absolutely did not changed anything in that pattern nor in the other OOB shared libraries. I only worked in the extension I created by myself.

I tried synchronize it again, putting back the extensions manually, but nothing worked, still the same error.

Is there a way to install back the OOB version of the pattern? Or do you have other solutions for this problem?

Just to be clear, I'm working only in DEV instance. Pattern in PROD instance is still working fine.

Thank you very much for your help.

[SiD2]

Hi @Au_an 

Really not sure behind the reason or can't pin point certainly here. One possibility that it could have happened is you might not have saved/published the extension and would have been in draft state and this could have happened.

However seems things have got corrupted, you can reinstall/repair the discovery plugin and it should be able to restore the OOB configuration.

If that works, then create your extension and save/publish and then do a pattern sync. Try and let me know if any help needed.

[Au_an]

Thank you very much for your answer SiD2,

The extension is still on service now, as well as all the others OOB extensions, they just disappeared from under the Extension Section of the Linux Server pattern after the sync. Apart from being a strange behavior, that was not much a problem because I was able to put back manually all the extensions as they were in the OOB configuration.

How can I reinstall/repair the discovery plugin?

Thank you.

[SiD2]

Hi @Au_an 

You can navigate to "System Definition->Plugins" in the filter navigator and search for the plugin. Have you not installed this in the first place?

[Au_an]

Actually I don't know. I work in a company and I'm not in charge of those things, I was only asked to create this extension.

Searching in that path, I found something called "Discovery and Service Mapping Patterns" that is installed in our instance, I think that patterns were installed from this plugin?

Isn't it possible to export the patter in the PROD instance and import it in the DEV one, without reinstall the entire plug in?