PREM issues table
Corrected issues | View the issues in the following tables by the default sort order, Status, which shows the corrected issues first. The version number represents the update Year.Month.Release or release number (MajorRelease.MinorRelease.ServicePack.Patch) in which the issue is fixed. |
|---|---|
Known (open) issues |
|
Known and corrected installation and upgrade issues
Component | Description | Status | Found in | Defect ID |
|---|---|---|---|---|
| Installation and Upgrade | Symptom: Discovery upgrade from 23.1 to 23.3 fails with the following error: "Inhibitor: Detected partitions mounted with the "noexec" option, preventing a successful in-place upgrade. | 25.2.00 | 23.1.00 | DRUD1-47073 |
Upgrade | Symptom: Upgrades fail if Baseline disk space monitoring is disabled. | 24.3.0.1 | 22.2.00, 23.1.00, 24.1.00, 24.2.00, 24.3.00 | DRUD1-50298 (DRUD1-49141, DRUD1-49872) |
Upgrade | Symptom: 23.3 Upgrade fails if an invalid yum.conf file exists. | 24.2.00 | 23.2.00 | DRUD1-43258 |
Installation and | Symptom: Appliance Specification shows a false positive for DB Disk Calculation after 23.3 Upgrade. | 24.1.00 | 23.2.00 | DRUD1-42428 |
Installation and | Symptom: The tw_https_generatekey utility does not work in BMC Discovery 23.3. | 24.1.00 | 23.3.00 | DRUD1-42534 |
Upgrade | Symptom: Oracle Linux 9 does not support v1 architecture CPUs. Documentation fix, see Preparing-for-upgrade. | 23.3.01 | 23.3.00 | DRUD1-42641/ DRUD1-41891 |
Upgrade | Symptom: The upgrade fails if you have any unused disks attached. Scope: The upgrade fails if you have any unused disks attached. An unused disk is, for example, one with no partitions defined, or one or more partitions defined and not mounted. | 23.3.00.1 | 23.3.00 | DRUD1-42351 |
Installation and | Symptom: The initial release of BMC Discovery 23.3 was not FIPS compliant, in new installations or upgrades. If you require FIPs compliance, you should upgrade to BMC Discovery 23.3 patch 1. | 23.3.00.1 | 23.3.00 | DRUD1-42410 |
Known and corrected product issues
Component | Description | Status | Found in | Defect ID |
|---|---|---|---|---|
Credentials | Problem: When an 11.x system with CyberArk installed is upgraded to 20.02.01, CyberArk stops functioning. An error message is displayed on the CyberArk Credential Provider tab: APPAP292E Unrecoverable error previously occurred. Avoiding approach to the Vault. Workaround: Re-authenticate the AIM provider with the CyberArk vault. | Open | 20.02.01 (12.0.0.1) | DRUD1-29491 |
Permissions | Problem: cmdb-export-administrator has insufficient permissions to view the export page. Workaround: Add vault/credentials/read permission to cmdb-export-administrator. | Open | 10.2.0.1, 11.0.0.0, 11.1.0.0 | DRUD1-19243 |
Discovery | Problem: In some rare, but repeatable, cases it has been observed that performing an SNMP discovery of Juniper ERX-1440 and Cisco 6500 network devices with over 2000+ virtual interfaces might cause CPU spikes on the network device, which in extreme cases can impact switching behavior. This has only been reported by one customer, and we have confirmed other instances where discovery of the same type of devices, with similar numbers of virtual interfaces did not trigger the problem. It is therefore not possible to say precisely when this problem may be triggered. Where you are aware that the models listed above are in your discovery environment, it is advisable to perform some test scans while monitoring the CPU load on the target device prior to setting up regular scans. If you are seeing CPU load on the above devices, you can consider testing these devices once with SNMP GETNEXT method rather than default SNMP GETBULK. | Open | 10.2.0.4 | DRUD1-17924 |
TPL | Problem: A break statement in a second nested if clause of the for loop causes pattern to stop. | Open | 10.1.0.0 | DRUD1-16014 |
UI | Problem: Query builder should allow Boolean selectors for non-taxonomy attributes. | Open | 10.0.0.3, 10.1.0.0 | DRUD1-15724 |
Model | Problem: Duplicate Hosts created when scanning Linux host with SNMP and SSH using different IPs. | Open | 9.0.0.0 | DRUD1-14389 |
Discovery | Problem: Appliances with less than 16GB memory might show the Technical difficulties page when performing cloud scans, particularly when performing concurrent scans. Workaround: Upgrade to at least 16GB if you are discovering cloud services. | Open | 23.3.00 | DRUD1-42092 |
Discovery | Problem: Currently if you discover Oracle Cloud Infrastructure (OCI) with BMC Discovery 23.3 (13.0), scan times are longer compared with previous versions of BMC Discovery. | Open | 23.3.00 | DRUD1-41504 |
Virtual appliance | Problem: Upgrading a virtual appliance on Hyper-V fails if the Hyper-V packages are still Installed on the virtual host. Note that Hyper-V is not an officially supported platform. Workaround: Remove the Hyper-V packages before upgrading to BMC Discovery 23.3. | Open | 23.3.00 | DRUD1-42089 |
| Cluster Manager | Symptom: Occasionally, a member cannot be added to a cluster after a revert to stand-alone. | 25.2.00 | 22.2.01 | DRUD1-42348 |
| CMDB-Sync | Symptom: Cloud Database nodes are not synchronized with ServiceNow CMDB. | 25.2.00 | 22.2.01 | DRUD1-42396 |
| CMDB-Sync | Symptom: CMDB Services Sync can remove relationships in Discovery while they are still present in the CMDB. | 25.2.00 | 24.3.00 | DRUD1-51175 |
| DataStore | Symptom: Online compaction on a multi-generational datastore should not run when only one read-only generation exists. | 25.2.00 | 24.3.00 | DRUD1-50845 |
| Discovery | Symptom: AssertionError in Discovery for failed SSH scan targets | 25.2.00 | 24.3.0.1 | DRUD1-51900 |
| Discovery | Symptom: Linux server fails with "NoAccess (Host identification failure - no mac addresses)" | 25.2.00 | 24.2.00 | DRUD1-51921 |
| Discovery | Symptom: The --scan-option-discover-desktops in the tw_scan_control does not work. | 25.2.00 | 24.3.00 | DRUD1-50347 |
| Discovery | Symptom: vCenter API does not return network interface information. | 25.2.00 | 24.2.00 | DRUD1-51282 |
| Documentation | Symptom: The documentation incorrectly states that "getNetworkConnectionList is not available using WMI." | 25.2.00 | 24.2.01 | DRUD1-50687 |
| Inferred Sync | Symptom: Receiver restart during inferred sync resync caused synced data to be destroyed. | 25.2.00 | 25.1.00 | DRUD1-51661 |
| Other/Unknown | Symptom: Daily Disk Usage Statistics graph is not updated after running tw_ds_compact. | 25.2.00 | 22.2.00 | DRUD1-38067 |
| Other/Unknown | Symptom: The chrony.conf file is losing some settings after modifying the NTP configuration. | 25.2.00 | 24.3.00 | DRUD1-51871 |
| Other/Unknown | Symptom: The license use of hosts created by BMC Helix Operations Management and BMC Helix Intelligent Integrations is unclear. | 25.2.00 | 22.3.01 | DRUD1-46557 |
| Reasoning | Symptom: The reasoning logs contain ecResyncCancelTasks failure messages. | 25.2.00 | 24.3.00 | DRUD1-50935 |
| Search | Symptom: Query function friendly_duration does not work as expected. XXX | 25.2.00 | 24.3.00 | DRUD1-51521 |
| Taxonomy | Symptom: The SoftwareInstance relationship role ElementUsingFile is not visible in visualizations. | 25.2.00 | 24.3.00 | DRUD1-51135 |
| UI | Symptom: A query generated by the Visual query builder with a "Before" condition fails to return the expected output. | 25.2.00 | 24.4.00 | DRUD1-51094 |
| UI | Symptom: Queries with parameters saved in "Favorite Queries" fail with "Invalid conditions". | 25.2.00 | 24.4.00 | DRUD1-51518 |
| UI | Symptom: While viewing a StorageSystem, the Technical difficulties page is displayed. | 25.2.00 | 25.1.00 | DRUD1-51272 |
| UI | Symptom: You should not be able to click the BMC Discovery Outpost credential import button multiple times. | 25.2.00 | 24.2.02 | DRUD1-50580 |
Discovery | Symptom: Occasionally, the DiscoveredCommandResult.result log might contain unexpected characters. | 24.3.0.1 | 24.2.02 | DRUD1-50672 (DRUD1-49808, DRUD1-49492, DRDC1-24140, DRUD1-50314) |
Discovery | Symptom: The last PowerShell and last WBEM heuristics do not include port information and do not make a connection.
| 24.3.0.1 | 24.2.00 | DRUD1-50671 (DRUD1-50322, DRUD1-50225, DRUD1-49955) |
REST API | Symptom: Deleting a Windows proxy by using the REST API does not entirely remove some proxy configuration on other cluster members. | 24.3.0.1 | 23.3.00 | DRUD1-50605 (DRUD1-50336) |
Discovery | Symptom: PowerShell scanning by using an older version of the Active Directory Proxy does not work. | 24.3.0.1 | 24.3.00 | DRUD1-50400 (DRUD1-50392, DRUD1-50390) |
Discovery | Symptom: Failure in session reconnect leaves a traceback in the .out file and reports UNKNOWN. | 24.3.0.1 | 24.3.00 | DRUD1-50401 (DRUD1-50393) |
Service Modeling | Symptom: The direction of some relationships between nodes is shown differently in the Node and Service views. | 24.3.0.1 | 24.4.01 | DRUD1-50591 (DRUD1-50584) |
Outpost | Symptom: The BMC Discovery Outpost logs workInProgress() errors. | 24.3.0.1 | 24.3.00 | DRUD1-50398 (DRUD1-49416, DRUD1-49728, DRUD1-49325, DRUD1-49543, DRUD1-49718, DRUD1-49339) |
Discovery | Symptom: When discovering a Windows host by using PowerShell, a Critical error and traceback is logged. | 24.3.0.1 | 24.2.01, 24.3.00 | DRUD1-50394 (DRUD1-49714) |
External Management REST API | Symptom: No response from REST API POST admin/upgrade. | 24.3.00 | 24.3.00 | DRUD1-48849 |
External Management REST API | Symptom: The REST API Upgrade endpoint provides no feedback when used with non-admin permissions. | 24.3.00 | 24.3.00 | DRUD1-49042 |
External Management REST API | Symptom: The REST API Upgrade endpoint does not distribute the upgrade package to all cluster members. | 24.3.00 | 24.3.00 | DRUD1-49239 |
CMDB sync | Symptom: A custom synchronization pattern fails with AttributeError: module 'cmdb_sync.functions' has no attribute 'hasSubword' during CMDB synchronization. | 24.2.02 | 24.3.00 | DRUD1-48712 |
Discovery | Symptom: Discovery by using SNMP occasionally fails (unable to get the deviceinfo UNKNOWN) after the May 2024 TKU update. | 24.2.00.1 | 23.3.00 | DRUD1-48803/ DRUD1-48749 |
CMDB sync | Symptom: While syncing to CMDB, a custom sync pattern fails with AttributeError: module 'cmdb_sync.functions' has no attribute 'hasSubword'. | 24.2.00.1 | 24.2.02 | DRUD1-48713/ DRUD1-48712 |
CMDB sync | Symptom: An unexpected number of CI updates occur when syncing a Host node twice. | 24.2.00.1 | 24.2.00 | DRUD1-48711/ DRUD1-48512 |
Consolidation | Symptom: "Request for information not part of the consolidated data" errors are logged by the Consolidator after 24.2 upgrade. | 24.2.00.1 | 23.2.00 | DRUD1-48444/ DRUD1-48442 |
Service and | Symptom: Destruction of nodes in a model causes a full model update, including when the model is in the review-suggested state. | 24.2.00.1 | 23.3.00 | DRUD1-48275/ DRUD1-48261 |
Discovery | Symptom: Errors reported by tw_winproxy_settings when unexpected settings are encountered. | 24.2.00 | 24.3.00 | DRUD1-47982 |
Discovery | Symptom: Linux hosts discovered by using BMC Discovery and those discovered from BMC Helix Operations Management can have a mismatch between MAC addresses and network interfaces, possibly resulting in duplicate hosts. | 24.2.00 | 24.3.00 | DRUD1-48254 |
CMDB sync | Symptom: Unexpected number of CIs updates when syncing a Host node twice. | 24.2.00 | 24.3.00 | DRUD1-48512 |
Reasoning | Symptom: The Contributor:Inference relationship should be deleted or updated when a Contributor package is updated. | 24.2.00 | 22.1.01 | DRUD1-40477 |
Discovery Outpost | Symptom: BMC Discovery Outpost SSH workers remain after a scan is finished. | 24.2.00 | 23.1.02 | DRUD1-43920 |
Disaster Recovery | Symptom: Disaster recovery cluster creation fails when the datastore is not in the default location. | 24.2.00 | 22.3.01.001 | DRUD1-46706 |
Reasoning | Symptom: FibreChannelPort and FiberChannelNode do not have a key. | 24.2.00 | 24.1.00 | DRUD1-43931 |
Discovery | Symptom: The JDBC embedded database drivers should be updated to the latest available version. | 24.2.00 | 21.02.00 | DRUD1-32207 |
Discovery | Symptom: The JDBC driver management page should be improved. | 24.2.00 | 24.1.00 | DRUD1-47083 |
Discovery | Symptom: SSM Setting on a scheduled Discovery Run cannot be changed to Disabled. | 24.2.00 | 23.3.00 | DRUD1-43057 |
Licensing | Symptom: The licensing page shows "Not Installed Storage Discovery" while Storage TKU is installed. | 24.2.00 | 23.3.01 | DRUD1-46828 |
CMDB sync | Symptom: Add option for Service sync in CMDB command line utility. | 24.2.00 | 23.4.00 | DRUD1-43398 |
Discovery Outpost | Symptom: Use the highest available cypher suites in theBMC Discovery Outpost. | 24.2.00 | 22.2.00 | DRUD1-38377 |
Discovery | Symptom: PowerShell discovery failure message is not helpful. | 24.2.00 | 22.2.00 | DRUD1-46439 |
UI | Symptom: When clicking on a host, the Discovery UI page displays: "This system is having technical difficulties with this page." | 24.2.00 | 22.2.01 | DRUD1-43579 |
Service and application modeling | Symptom: When changing a value in Visual Query condition builder, object Object is displayed in text field. | 24.2.00 | 24.1.02 | DRUD1-46754 |
UI | Symptom: Dashboard Deselect Function does not deselect the checkbox for a custom channel. | 24.2.00 | 22.2.00 | DRUD1-40019 |
Service and application modeling | Symptom: Creating a Service using Blueprint is not setting 'compatibility' on ModelDefinition node. | 24.2.00 | 24.1.02 | DRUD1-47415 |
Discovery | Symptom: Cloud detection platform script flags use ksh construct. | 24.2.00 | 23.3.00.001 | DRUD1-47499 |
Discovery | Symptom: Oracle SQL queries should follow the DB credential timeout. | 24.2.00 | 22.2.00 | DRUD1-39998 |
Discovery | Symptom: The gce_instance_name is set on some AWS Hosts. | 24.2.00 | 23.4.00 | DRUD1-43523 |
Reasoning | Symptom: TPL multi-hop key expression does not reproduce semantics of previous versions. | 24.2.00 | 24.2.00 | DRUD1-47601 |
UI | Symptom: On CMDB timeouts, an unhelpful technical error was displayed in the UI. The error is now replaced with a simple message. | 24.1.00 | 22.2.00.1 | DRUD1-41552 |
UI | Symptom: You cannot bulk delete Recognition Rules, or sort rules in the UI according to Status. Controls have been added to enable you to do so. See Recognizing-SNMP-devices for more information. | 24.1.00 | 22.2.00 | DRUD1-41491 |
Discovery Outpost | Symptom: SinceBMC Discovery Outpost 867818, connection to the Hashicorp credential vault fails. | 24.1.00 | 23.2.00 | DRUD1-42843 |
External Management REST API | Symptom: The REST API did not honor maintenance mode. Any modifying (non-GET) request returns 403 Forbidden if the system is in maintenance mode. | 24.1.00 | 22.1.01 | DRUD1-42324 |
Discovery | Symptom: If a baseline check was run between a tw_options change and the "Updated options..." message, a TypeError exception was was raised, and the Cluster Manager required restarting. | 24.1.00 | 22.1.00 | DRUD1-42297 |
UI | Symptom: A custom taxonomy causes a 'This system is having technical difficulties...' page. | 24.1.00 | 23.1.00 | DRUD1-42561 |
Discovery Outpost | Symptom: When the BMC Discovery Outpost released with the November TKU is installed on a FIPS enabled host, if it is not installed in the C:\ drive, the installation/upgrade does not place the fips.conf file correctly. | 24.1.00 | 23.1.00 | DRUD1-43256 |
UI | Symptom: HTML bold font code is visible when searching for ModelDefinitions. | 24.1.00 | 23.3.00 | DRUD1-43119 |
Reasoning | Symptom: External events are not sent by consolidation. | 24.1.00 | 23.3.00 | DRUD1-43342 |
Discovery Outpost | Symptom: BMC Discovery Outpost connection through proxy does not work until name resolution is available from the BMC Discovery Outpost. | 24.1.00 | 23.4.00 | DRUD1-43456 |
UI | Symptom: The tw_svc_cluster_manager.log shows security.api: WARNING: User 'xxxxxx' does not have permission for operation 'cmdb_sync' | 24.1.00 | 23.1.00 | DRUD1-42587 |
UI | Symptom: The title is missing on the query result list when executed from User Queries or From Favorite Queries. | 24.1.00 | 21.05.00 | DRUD1-35214 |
Vault | Symptom: In certain rare upgrade failures, the vault could become inaccessible. This has been corrected. | 24.1.00 | 23.2.00 | DRUD1-43484 |
Discovery | Symptom: Discovering Citrix NetScaler devices by using the REST API fails after installing the November TKU. | 24.1.00 | 23.3.00 | DRUD1-43492 |
CMDB sync | Symptom: When processing CMDB Filters, sometimes the sync will fail, and a RecursionError: maximum recursion depth exceeded error is written to the logs. | 23.4.02 | 24.3.00 | DRUD1-46967 |
Discovery | Symptom: When discovering an Oracle database that is using service names, the BMC Discovery Outpost cannot connect. | 23.4.00 | 24.3.00 | DRUD1-43413 |
Service and application modeling | Symptom: In Start Anywhere Modeling, the "Do not follow any connection" rule should include the "Management" relationship. | 23.3.01 | 22.2.01, 23.3.00.001 | DRUD1-42708/ DRUD1-42057 |
UI | Symptom: The sizing information was changed in the BMC Discovery 23.3 documentation, it is now reflected in the UI. | 23.3.01 | 23.3.00 | DRUD1-42693/ DRUD1-42245 |
Baseline | Symptom: In certain circumstances, the following Baseline error occurs: FAILED: Exception Raised: TypeError: '<=' not supported between instances of 'Any and 'int'. | 23.3.01 | 22.1.00, 22.2, 23.1 | DRUD1-42685/ DRUD1-42297 |
Discovery | Symptom: SSH scans using keys through the Outpost do not work since the upgrade to BMC Discovery Outpost 867818 (Sep 2023 TKU). | 23.3.01 | 23.2.00 | DRUD1-42676/ DRUD1-42631 |
Baseline | Problem: The appliance baseline feature uses a third-party software tool called Tripwire. The Tripwire packages are not included in the initial release of the BMC Discovery 23.3. Workaround: To re-enable Tripwire, contact BMC Customer Support. | 23.3.01 | 23.3.00 | DRUD1-42162 |
Clusters | Symptom: Generating new keys by using the HTTPS Configuration page in a cluster allows you to partially apply changes. | 23.3.00 | 24.3.00 | DRUD1-42812 |
Netadmin | Symptom: Default gateway address is not configured after static IP address is set by using the netadmin user. | 23.3.00 | 24.3.00 | DRUD1-43063 |
Discovery | Symptom: You cannot perform a scan assuming all IP addresses are active, and skip pre-scanning. A new option is added in the Add a New Run dialog. | 23.3.00 | 24.3.00 | DRUD1-47363 |
Discovery | Symptom: Guest and ESX hosts are missing when vCenter is scanned with option "VMware Guest Scanning" enabled. | 23.3.00 | 24.3.00 | DRUD1-47940 |
Discovery | Symptom: Windows host names with more than 15 characters are truncated when discovered by using Powershell. | 23.3.00 | 24.3.00 | DRUD1-47963 |
Service and application modeling | Symptom: Destruction of nodes in a model causes a full update of the model, even if it is in the review-suggested state. | 23.3.00 | 24.3.00 | DRUD1-48261 |
Discovery | Symptom: Random SNMP failures (unable to get the deviceinfo UNKONWN) after May TKU/BMC Discovery Outpost update. | 23.3.00 | 24.3.00 | DRUD1-48749 |
Documentation | Scope: A link is displayed to a report of CIs awaiting incremental resync, though the link is not documented. | 23.3.00 | 11.3 | DRUD1-23565 |
Windows proxy | Symptom: Multiple processes running on the Proxy server are not being killed, resulting in the server requiring a reboot. Workaround: Reboot the proxy server. | 23.3.00 | 11.3.00 | DRUD1-30304 |
Discovery | Symptom: During the discovery pre-scan phase with Nmap, many non-existent, unsupported devices were being created. | 23.3.00 | 11.2.00.6, | DRUD1-31351 |
Datastore | Symptom: An excessively long query could occasionally result in the following ECA error: RuleError on rule reasoning_host_create_if_necessary. | 23.3.00 | 20.08.01 | DRUD1-31727 |
Discovery | Symptom: The DiscoveryRun node cannot attach to the DataSourceAccess node when a custom pattern triggers on the same DiscoveryRun node. | 23.3.00 | 21.02.00 | DRUD1-32538 |
CMDB sync | Symptom: CMDB resync may occasionally use excessive memory and the resync fail. | 23.3.00 | 21.05.01 | DRUD1-33393 |
Discovery | Symptom: The Solaris serial is not discovered when the sneep utility is not in /opt/SUNWsneep/bin. Workaround: Modify the path on the Solaris host to include the location of the sneep utility. | 23.3.00 | 21.3 | DRUD1-36534 |
Outpost | Symptom: Windows cannot start the Outpost Service. Workaround: Keep the 'Adjust for daylight saving time automatically' setting enabled on the Outpost host date-time settings. | 23.3.00 | 22.1.01 | DRUD1-37180 |
Cluster | Symptom: Applying a wildcard HTTPS certificate prevents the cluster service starting after reboot. | 23.3.00 | 22.1.01 | DRUD1-37449 |
Outpost | Symptom: Outpost login page unresponsive after vulnerability scan using Qualys. Workaround: Restart the Outpost service. | 23.3.00 | 20.08.01 | DRUD1-37923 |
Discovery | Symptom: Database discovery attempts to use disabled credentials. Workaround: Remove the disables credentials. | 23.3.00 | 22.2.00 | DRUD1-38387 |
Discovery | Symptom: There is no detail within model Activity Record for some node kinds. | 23.3.00 | 22.2.01 | DRUD1-38847 |
Discovery | Symptom: Windows package names can contain garbage characters. | 23.3.00 | 20.08.00 | DRUD1-38879 |
UI | Symptom: Where scans contain very many, links might be generated and displayed that are too long to be served in the UI. | 23.3.00 | 22.1.01 | DRUD1-39226 |
Discovery | Symptom: The token for the Thycotic Secret Server credential broker expires after 20 minutes leading to scan failures. | 23.3.00 | 21.3.00 | DRUD1-39596 |
Credentials | Symptom: Unable to load credentials when the Enter key is used instead of the Apply button when creating or editing a credential in the BMC Discovery Outpost. Workaround: Use the Apply button in the UI when creating credentials in the BMC Discovery Outpost. | 23.3.00 | 21.05.00, | DRUD1-39597 |
Logging | Symptom: Audit Log did not record login failure for user without correct permission. | 23.3.00 | 22.2.00 | DRUD1-39641 |
Discovery | Symptom: The tw_proxy_register utility cannot register an existing proxy with another appliance. | 23.3.00 | 22.2.01 | DRUD1-39798 |
Discovery | Symptom: Occasionally Amazon Web Services fails with the ECA error, inference is None in InferenceKeyMaintainer.extract_keys(). | 23.3.00 | 22.2.00 | DRUD1-39802 |
Discovery | Symptom: Deep discovery of VMware Guest Hosts performs unnecessary implicit scans of the vCenter guest. | 23.3.00 | 22.2.00.1 | DRUD1-39805 |
Credentials | Symptom: PowerShell credential failures are not recorded in the UI Session Result List. | 23.3.00 | 22.1.00 | DRUD1-39829 |
Discovery | Symptom: Discovery of OpenVMS using ssh from the BMC Discovery Outpost fails. | 23.3.00 | 23.1.00 | DRUD1-39902 |
Discovery | Symptom: Explicit and Implicit scans of the same endpoint result in a successful and an unsuccessful scan linked to the Discovery Access. | 23.3.00 | 23.1.00 | DRUD1-40107 |
Discovery | Symptom: vCenter polling can stop when the SI starts to age. | 23.3.00 | 23.1.00 | DRUD1-40114 |
UI | Symptom: The Host node view page shows a table of network interfaces and their IP addresses. If there are no network interfaces, no IP address information is shown. | 23.3.00 | 23.1.00 | DRUD1-40243 |
Discovery | Symptom: Discovery Run errors are shown on LPARs when a Job Name is not reported. | 23.3.00 | 22.2.00 | DRUD1-40268 |
Credentials | Symptom: You cannot extract DOMAIN from Cyberark from an arbitrary attribute. See Using-CyberArk-credentials-for-discovery for more information on this resolved defect. | 23.3.00 | 11.3 | DRUD1-40301 |
Consolidation | Symptom: Recent run in Consolidator shows an error regarding "Outpost no longer registered". | 23.3.00 | 23.1.00 | DRUD1-40320 |
Outpost | Symptom: The BMC Discovery Outpost automatic update occasionally fails resulting in a BMC Discovery Outpost that can no longer connect to BMC Helix Discovery. The installation failure is not logged. Workaround: Perform a manual update of the BMC Discovery Outpost. | 23.3.00 | 22.1.01 | DRUD1-40329 |
CMDB sync | Symptom: The last_discovered attribute should be set when a destroyed node is synced to ServiceNow CMDB. | 23.3.00 | 22.1.00 | DRUD1-40421 |
Model | Symptom: SIs hosted on MFParts do not age correctly. | 23.3.00 | 23.1.00 | DRUD1-40594 |
Documentation | Scope: The Discovering-VMware-guest-hosts-by-using-the-vCenter-API topic does not mention of VMware tool requirement. | 23.3.00 | 23.1.00 | DRUD1-40868 |
Documentation | Scope: The PRIV_LSHW privileged command was not documented. | 23.3.00 | 23.1.00 | DRUD1-40899 |
Modeling | Symptom: You cannot use Google Chrome or Microsoft Edge to export a SAM model definition if there is a comma in the name. Workaround: Use the Firefox browser or edit the model definition name. | 23.3.00 | 22.2.01 | DRUD1-40900 |
Key generation | Symptom: Cannot generate a new key when the company name is too long. | 23.3.00 | 23.1.00 | DRUD1-40932 |
Discovery | Symptom: Intermittent inconsistent Kerberos scan failures occur in a cluster (in time, and by member) after upgrade from 22.2.0.2 to 23.1.0.1. | 23.3.00 | 22.2.0.2 | DRUD1-40935 |
Documentation | Scope: Documentation error in the tw_pattern_management topic. | 23.3.00 | 23.1.01 | DRUD1-41221 |
TPL | Symptom: The discovery.getCertificate() TPL function does not handle timeouts correctly. | 23.3.00 | 23.1.00 | DRUD1-41408 |
Credentials | Symptom: If you add a comma separated IP address with line breaks in Matching criteria or Matching exceptions, and you do not use the text view toggle, you cannot test the credential. Workaround: Avoid line breaks in a list of IP addresses of you are pasting them into the IP Address field. | 23.3.00 | 23.1.02 | DRUD1-41505 |
UI | Symptom: The visualization screen times out when displaying Storage in the infrastructure focus. | 23.3.00 | 23.1.00 | DRUD1-41803 |
Appliance | Symptom: The Appliance Specification shows a false positive for DB Disk Calculation after upgrading to BMC Discovery 23.3. | 23.2.00 | 24.3.00 | DRUD1-42428 |
Consolidation | Symptom: "Request for information not part of the consolidated data" error is seen on the Consolidator after upgrading to BMC Discovery 24.2. | 23.2.00 | 24.3.00 | DRUD1-48442 |
Outpost | Symptom: The BMC Discovery Outpost can leave child Java processes after running SQL queries. | 23.1.00 | 24.3.00 | DRUD1-42656 |
CMDB sync | Symptom: If a ServiceNow CMDB sync connection times out, it can cause cluster problems. | 23.1.00 | 24.3.00 | DRUD1-43073 |
Discovery | Symptom: SSM connections do not honour the TLS certification check setting in the AWS credential. | 23.1.00 | 24.3.00 | DRUD1-46701 |
Discovery | Symptom: Expired Kerberos credentials can block good scans with 30 min timeouts. | 22.3.00 | 24.3.00 | DRUD1-47007 |
Discovery | Symptom: Discovery requests against Hosts that were not created by session-based access can fail and result in errors. | 22.1.00.1 | 24.3.00 | DRUD1-37370 |
Netadmin | Symptom: The netadmin user does not support defining a static IPv6 address. | 21.05.00 | 24.3.00 | DRUD1-33709 |
Backup | Symptom: Encrypted backups cannot be restored by using the tw_restore utility. Workaround: Use the UI to restore backups. |
| 23.3.00 | DRUD1-42091 |