- Welcome BMC Customer Support Site Guest User
Knowledge Article
Discovery: Pattern Activation Failed / does not match required version / does not contain function/ TKU upgrade fails with "Pattern Upload Failed"
Discovery: Pattern Activation Failed / does not match required version / does not contain function/ TKU upgrade fails with "Pattern Upload Failed"
BMC Discovery
BMC Discovery
All Versions
When uploading a TKU, the following messages are observed: Change to module <module name> failed because imported name <name> version <version1> from <name> does not match required version <version2> at line <line number>
Pattern Activation Failed
|
Root cause 1: Mismatch between the TKU version and the Discovery version. For example: a TKU for 21.3 was installed on Discovery 11.3
Solution: chose a TKU version suitable for your Discovery version. For example: on Discovery 21.3, use a TKU for 21.3. For more details, see the article below: Root cause 2: A custom pattern depends on something that changed, it caused a dependency issue. For example: the version of a PatternModule version or a function changed while it was used by a custom pattern. If if this happens after a TKU ugprade, it suggest the custom pattern is not compatible anymore with the TKU: it depends on something that the TKU tries to change or remove.
Solution: - Temporarily deactivate the custom patterns that are mentioned in the error messages - Activate all TKU patterns - adapt the custom patterns to the TKU. Here is a use case to illustrate this root cause/solution: Let's say that
- the TKU OOTB pattern module CMDB.Device_Endpoints contains the pattern Device_Endpoints version 1.1 - a custom syncmpapping named CMDB.Extension.BMC_LANEndpoint_extend was successfully activated - it contains the line below 45 from CMDB.Device_Endpoints import Device_Endpoints 1.1; - a TKU upgrade is executed - it tries to update Device_Endpoints and modify the version from 1.1 to 2.2 It will logically fail with the error below: Change to module CMDB.Extension.BMC_LANEndpoint_extend failed because Imported name ‘Device_Endpoints’ version 2.2 from CMDB.Device_Endpoints does not match required version 1.1 at line 45.
To resolve the dependency issue between the customization an the new TKU, the designer of the custom pattern must: - disable CMDB.Extension.BMC_LANEndpoint_extend - upgrade the TKU again and let it change the version of Device_Endpoints and modify the version from 1.1 to 2.2 - edit CMDB.Extension.BMC_LANEndpoint_extend and replace 45 from CMDB.Device_Endpoints import Device_Endpoints 1.1; by 45 from CMDB.Device_Endpoints import Device_Endpoints 2.2; - activate CMDB.Extension.BMC_LANEndpoint_extend |
Attachment(s):