Page Properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
Filter by
Discovery
Problem | Short description | Description | Steps to reproduce |
---|---|---|---|
Discovery PRB1343838 | This PRB fix addresses a New York Patch 3 issue where Cloud Discovery would fail when the Discovery plugin is not activated | ||
Discovery PRB1364492 | After clicking 'Discover now' on any discovery schedule, the page keeps loading and the discovery does not start |
Notice that the discovery does not start and the pop-up window keeps loading. In the console, the following error appears: 'Script: DiscoveryAjax not found in scope: global, and HTTP Processor class not found: com.glide. processors.xmlhttp.DiscoveryAjax: no thrown error'. Note: Only Cloud Management Core and Cloud Management are activated here. | |
Discovery PRB1365469 | Errors occur for Horizontal DiscoveryResult Handler.update DeviceHistory() when the CI does not have the name and the ip_address populated | Refer to the listed KB article for details. | |
Discovery PRB1366194 | Patterns SSH sudo command using CyberArk with no credential ID fails | For the SSH credential saved on CyberArk, if users do not use the credential ID for the credential defined on the instance, when using patterns:
| |
Discovery PRB1367623 | The Windows OS - Desktops pattern sensor fails with the error 'Cannot deserialize object' | Refer to the listed KB article for details. |
...